VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@standardnotes/snjs: vulnerability history, versions and safety

@standardnotes/snjs is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the npm ecosystem.

i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all @standardnotes/snjs vulnerabilities

Vulert verdict on @standardnotes/snjs 2.212.4 i

Updated on 23 Oct 2026

Good news: 2.212.4, the version you would install today, has no known vulnerabilities.

Package health score 85/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Not enough data

What to do: Stay on 2.212.4 or newer. This can change: a vulnerability disclosed tomorrow can affect 2.212.4 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 2.212.4 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 1 packages i
  • Last release 1 month ago i
  • Licence AGPL-3.0 i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for @standardnotes/snjs, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
2.212.4 15 Sep 2026 none AGPL-3.0 — Details →
2.212.3 04 Sep 2026 none AGPL-3.0 — Details →
2.211.6 23 Apr 2026 none AGPL-3.0 — Details →
2.211.1 06 Nov 2025 none AGPL-3.0 — Details →
2.211.0 04 Nov 2025 none AGPL-3.0 — Details →
2.210.0 25 Sep 2025 none AGPL-3.0 — Details →
2.209.14 12 Sep 2025 none AGPL-3.0 — Details →
2.209.13 26 Aug 2025 none AGPL-3.0 — Details →
2.209.12 15 Jul 2025 none AGPL-3.0 — Details →
2.209.11 24 Jun 2025 none AGPL-3.0 — Details →
2.209.10 18 Jun 2025 none AGPL-3.0 — Details →
2.209.9 16 Jun 2025 none AGPL-3.0 — Details →
2.209.8 02 May 2025 none AGPL-3.0 — Details →
2.209.7 02 May 2025 none AGPL-3.0 — Details →
2.209.6 22 Nov 2024 none AGPL-3.0 — Details →
2.209.5 20 Sep 2024 none AGPL-3.0 — Details →
2.209.4 09 Sep 2024 none AGPL-3.0 — Details →
2.209.3 22 May 2024 none AGPL-3.0 — Details →
2.209.2 07 May 2024 none AGPL-3.0 — Details →
2.209.1 06 May 2024 none AGPL-3.0 — Details →
2.209.0 24 Apr 2024 none AGPL-3.0 — Details →
2.208.22 20 Apr 2024 none AGPL-3.0 — Details →
2.208.21 19 Apr 2024 none AGPL-3.0 — Details →
2.208.20 15 Apr 2024 none AGPL-3.0 — Details →
2.208.19 13 Apr 2024 none AGPL-3.0 — Details →
2.208.18 10 Apr 2024 none AGPL-3.0 — Details →
2.208.17 10 Apr 2024 none AGPL-3.0 — Details →
2.208.16 08 Apr 2024 none AGPL-3.0 — Details →
2.208.15 26 Mar 2024 none AGPL-3.0 — Details →
2.208.14 22 Mar 2024 none AGPL-3.0 — Details →
2.208.13 14 Mar 2024 none AGPL-3.0 — Details →
2.208.12 11 Mar 2024 none AGPL-3.0 — Details →
2.208.11 11 Mar 2024 none AGPL-3.0 — Details →
2.208.10 07 Mar 2024 none AGPL-3.0 — Details →
2.208.9 06 Mar 2024 none AGPL-3.0 — Details →
2.208.8 05 Mar 2024 none AGPL-3.0 — Details →
2.208.7 01 Mar 2024 none AGPL-3.0 — Details →
2.208.6 01 Mar 2024 none AGPL-3.0 — Details →
2.208.5 01 Mar 2024 none AGPL-3.0 — Details →
2.208.4 01 Mar 2024 none AGPL-3.0 — Details →
2.208.3 26 Feb 2024 none AGPL-3.0 — Details →
2.208.2 22 Feb 2024 none AGPL-3.0 — Details →
2.208.1 19 Feb 2024 none AGPL-3.0 — Details →
2.208.0 17 Feb 2024 none AGPL-3.0 — Details →
2.207.1 08 Feb 2024 none AGPL-3.0 — Details →
2.207.0 02 Feb 2024 none AGPL-3.0 — Details →
2.206.0 27 Jan 2024 none AGPL-3.0 — Details →
2.205.2 24 Jan 2024 none AGPL-3.0 — Details →
2.205.1 23 Jan 2024 none AGPL-3.0 — Details →
2.205.0 20 Jan 2024 none AGPL-3.0 — Details →
2.204.16 12 Jan 2024 none AGPL-3.0 — Details →
2.204.15 11 Jan 2024 none AGPL-3.0 — Details →
2.204.14 06 Jan 2024 none AGPL-3.0 — Details →
2.204.13 06 Jan 2024 none AGPL-3.0 — Details →
2.204.12 05 Jan 2024 none AGPL-3.0 — Details →
2.204.11 02 Jan 2024 none AGPL-3.0 — Details →
2.204.10 28 Dec 2023 none AGPL-3.0 — Details →
2.204.9 28 Dec 2023 none AGPL-3.0 — Details →
2.204.8 22 Dec 2023 none AGPL-3.0 — Details →
2.204.7 12 Dec 2023 none AGPL-3.0 — Details →
2.204.6 11 Dec 2023 none AGPL-3.0 — Details →
2.204.5 05 Dec 2023 none AGPL-3.0 — Details →
2.204.4 05 Dec 2023 none AGPL-3.0 — Details →
2.204.3 04 Dec 2023 none AGPL-3.0 — Details →
2.204.2 04 Dec 2023 none AGPL-3.0 — Details →
2.204.1 04 Dec 2023 none AGPL-3.0 — Details →
2.204.0 30 Nov 2023 none AGPL-3.0 — Details →
2.203.2 30 Nov 2023 none AGPL-3.0 — Details →
2.203.1 30 Nov 2023 none AGPL-3.0 — Details →
2.203.0 29 Nov 2023 none AGPL-3.0 — Details →
2.202.113 27 Nov 2023 none AGPL-3.0 — Details →
2.202.112 24 Nov 2023 none AGPL-3.0 — Details →
2.202.111 24 Nov 2023 none AGPL-3.0 — Details →
2.202.110 23 Nov 2023 none AGPL-3.0 — Details →
2.202.109 08 Nov 2023 none AGPL-3.0 — Details →
2.202.108 06 Nov 2023 none AGPL-3.0 — Details →
2.202.107 04 Nov 2023 none AGPL-3.0 — Details →
2.202.106 03 Nov 2023 none AGPL-3.0 — Details →
2.202.105 02 Nov 2023 none AGPL-3.0 — Details →
2.202.104 30 Oct 2023 none AGPL-3.0 — Details →
2.202.103 26 Oct 2023 none AGPL-3.0 — Details →
2.202.102 25 Oct 2023 none AGPL-3.0 — Details →
2.202.101 23 Oct 2023 none AGPL-3.0 — Details →
2.202.100 23 Oct 2023 none AGPL-3.0 — Details →
2.202.99 19 Oct 2023 none AGPL-3.0 — Details →
2.202.98 18 Oct 2023 none AGPL-3.0 — Details →
2.202.97 17 Oct 2023 none AGPL-3.0 — Details →
2.202.96 09 Oct 2023 none CC-BY-NC-SA-4.0 — Details →
2.202.95 05 Oct 2023 none CC-BY-NC-SA-4.0 — Details →
2.202.94 02 Oct 2023 none CC-BY-NC-SA-4.0 — Details →
2.202.93 29 Sep 2023 none CC-BY-NC-SA-4.0 — Details →
2.202.92 28 Sep 2023 none CC-BY-NC-SA-4.0 — Details →
2.202.91 26 Sep 2023 none CC-BY-NC-SA-4.0 — Details →
2.202.90 26 Sep 2023 none CC-BY-NC-SA-4.0 — Details →
2.202.89 26 Sep 2023 none CC-BY-NC-SA-4.0 — Details →
2.202.88 25 Sep 2023 none CC-BY-NC-SA-4.0 — Details →
2.202.87 22 Sep 2023 none CC-BY-NC-SA-4.0 — Details →
2.202.86 22 Sep 2023 none CC-BY-NC-SA-4.0 — Details →
2.202.85 22 Sep 2023 none CC-BY-NC-SA-4.0 — Details →
2.202.84 22 Sep 2023 none CC-BY-NC-SA-4.0 — Details →
2.202.83 21 Sep 2023 none — — Details →
2.202.82 20 Sep 2023 none — — Details →
2.202.81 20 Sep 2023 none — — Details →
2.202.80 20 Sep 2023 none — — Details →
2.202.79 20 Sep 2023 none — — Details →
2.202.78 19 Sep 2023 none — — Details →
2.202.77 19 Sep 2023 none — — Details →
2.202.76 18 Sep 2023 none — — Details →
2.202.75 15 Sep 2023 none — — Details →
2.202.74 15 Sep 2023 none — — Details →
2.202.73 15 Sep 2023 none — — Details →
2.202.72 13 Sep 2023 none — — Details →
2.202.71 12 Sep 2023 none — — Details →
2.202.70 12 Sep 2023 none — — Details →
2.202.69 08 Sep 2023 none — — Details →
2.202.68 07 Sep 2023 none — — Details →
2.202.67 07 Sep 2023 none — — Details →
2.202.66 06 Sep 2023 none — — Details →
2.202.65 05 Sep 2023 none — — Details →
2.202.64 04 Sep 2023 none — — Details →

The newest 120 of 933 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for @standardnotes/snjs

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About @standardnotes/snjs

Is @standardnotes/snjs safe to use?

Vulert has no vulnerabilities on record for @standardnotes/snjs in npm at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is @standardnotes/snjs's Vulert package health score?

Vulert scores @standardnotes/snjs 85/100, which reads as healthy. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of @standardnotes/snjs affected?

No. 2.212.4, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of @standardnotes/snjs should I use?

2.212.4 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does @standardnotes/snjs have?

0 vulnerabilities are recorded for @standardnotes/snjs in the npm ecosystem: 0 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new @standardnotes/snjs vulnerabilities disclosed?

0 vulnerabilities were recorded for @standardnotes/snjs in the last 12 months. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of @standardnotes/snjs are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor @standardnotes/snjs for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @standardnotes/snjs version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.