Vulnerability Database · npm · Package report

@standardnotes/time: vulnerability history, versions and safety

Q: How do I monitor @standardnotes/time for upcoming vulnerabilities?

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

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

0 vulnerabilities recorded

Nothing recorded for this package in the npm ecosystem.

0 with no fix published

Every vulnerability has a patched version to move to.

0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →

0 malicious-package vulnerabilities

No published version shipped hostile code.

See all @standardnotes/time vulnerabilities

Vulert verdict on @standardnotes/time 1.19.1 i

Updated on 23 Oct 2026

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

Package health score 69/100

Security No known security issues
Maintenance Slowing
Popularity Niche
Community Moderate

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

Current release 1.19.1 — unaffected i
Vulnerabilities on record 0 i
Highest CVSS n/a i
With no published fix 0 i
Depended on by 5 packages i
Stars 476 i
Last release 28 months ago i
Licence AGPL-3.0-or-later 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.

Scan your app free →

01 Versions

Which versions are affected

Every version Vulert tracks for @standardnotes/time, 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.

Version	Released	Vulert vulnerabilities	Licence	Fix published	Details
1.19.1	18 Jun 2024	none	AGPL-3.0-or-later	—	Details →
1.19.0	04 Jan 2024	none	AGPL-3.0-or-later	—	Details →
1.18.2	28 Dec 2023	none	AGPL-3.0-or-later	—	Details →
1.18.1	27 Nov 2023	none	AGPL-3.0-or-later	—	Details →
1.17.0	28 Sep 2023	none	AGPL-3.0-or-later	—	Details →
1.16.0	26 Sep 2023	none	AGPL-3.0-or-later	—	Details →
1.15.3	04 Sep 2023	none	AGPL-3.0-or-later	—	Details →
1.15.2	01 Sep 2023	none	AGPL-3.0-or-later	—	Details →
1.15.1	31 Aug 2023	none	AGPL-3.0-or-later	—	Details →
1.15.0	24 Aug 2023	none	AGPL-3.0-or-later	—	Details →
1.14.6	01 Jun 2023	none	AGPL-3.0-or-later	—	Details →
1.14.3	05 May 2023	none	AGPL-3.0-or-later	—	Details →
1.14.2	23 Feb 2023	none	AGPL-3.0-or-later	—	Details →
1.14.1	20 Jan 2023	none	AGPL-3.0-or-later	—	Details →
1.14.0	14 Nov 2022	none	AGPL-3.0-or-later	—	Details →
1.13.3	14 Nov 2022	none	AGPL-3.0-or-later	—	Details →
1.13.0	02 Nov 2022	none	AGPL-3.0-or-later	—	Details →
1.12.0	19 Oct 2022	none	AGPL-3.0-or-later	—	Details →
1.11.1	06 Oct 2022	none	AGPL-3.0-or-later	—	Details →
1.11.0	06 Sep 2022	none	AGPL-3.0-or-later	—	Details →
1.10.0	05 Sep 2022	none	AGPL-3.0-or-later	—	Details →
1.9.1	12 Jul 2022	none	AGPL-3.0-or-later	—	Details →
1.9.0	06 Jul 2022	none	AGPL-3.0-or-later	—	Details →
1.7.1	23 Jun 2022	none	AGPL-3.0-or-later	—	Details →
1.7.0	30 May 2022	none	AGPL-3.0-or-later	—	Details →
1.6.10	30 May 2022	none	AGPL-3.0-or-later	—	Details →
1.6.9	04 May 2022	none	AGPL-3.0-or-later	—	Details →
1.6.8	04 May 2022	none	AGPL-3.0-or-later	—	Details →
1.6.7	22 Apr 2022	none	AGPL-3.0-or-later	—	Details →
1.6.6	15 Apr 2022	none	AGPL-3.0-or-later	—	Details →
1.6.5	11 Apr 2022	none	AGPL-3.0-or-later	—	Details →
1.6.4	31 Mar 2022	none	AGPL-3.0-or-later	—	Details →
1.6.3	28 Feb 2022	none	AGPL-3.0-or-later	—	Details →
1.6.2	28 Feb 2022	none	AGPL-3.0-or-later	—	Details →
1.6.1	10 Feb 2022	none	AGPL-3.0-or-later	—	Details →
1.6.0	09 Feb 2022	none	AGPL-3.0-or-later	—	Details →
1.5.0	09 Feb 2022	none	AGPL-3.0-or-later	—	Details →
1.4.5	29 Dec 2021	none	AGPL-3.0-or-later	—	Details →
1.4.4	29 Dec 2021	none	AGPL-3.0-or-later	—	Details →
1.4.2	29 Dec 2021	none	AGPL-3.0-or-later	—	Details →
1.4.1	29 Dec 2021	none	AGPL-3.0-or-later	—	Details →
1.4.1-beta-testing.0	23 Dec 2021	none	AGPL-3.0-or-later	—	Details →
1.3.3	23 Dec 2021	none	AGPL-3.0-or-later	—	Details →
1.3.2	23 Dec 2021	none	AGPL-3.0-or-later	—	Details →
1.4.0	23 Dec 2021	none	AGPL-3.0-or-later	—	Details →
1.3.1	23 Dec 2021	none	AGPL-3.0-or-later	—	Details →
1.3.0	23 Dec 2021	none	AGPL-3.0-or-later	—	Details →
1.2.4	23 Dec 2021	none	AGPL-3.0-or-later	—	Details →
1.2.3	23 Dec 2021	none	AGPL-3.0-or-later	—	Details →
1.2.2	23 Dec 2021	none	AGPL-3.0-or-later	—	Details →
1.2.1	22 Dec 2021	none	AGPL-3.0-or-later	—	Details →
1.2.0	22 Dec 2021	none	AGPL-3.0-or-later	—	Details →
1.2.0-beta.0	22 Dec 2021	none	AGPL-3.0-or-later	—	Details →
1.1.0	22 Dec 2021	none	AGPL-3.0-or-later	—	Details →
1.0.5	21 Dec 2021	none	AGPL-3.0-or-later	—	Details →
1.0.5-beta.0	21 Dec 2021	none	AGPL-3.0-or-later	—	Details →
1.0.5-beta-fix-deployment.0	20 Dec 2021	none	AGPL-3.0-or-later	—	Details →
1.0.5-beta-lock-protected-note-if-session-expired-2.0	20 Dec 2021	none	AGPL-3.0-or-later	—	Details →
1.0.5-beta-lock-protected-note-if-session-expired.0	17 Dec 2021	none	AGPL-3.0-or-later	—	Details →
1.0.5-beta-settings-version-upgrade.0	16 Dec 2021	none	AGPL-3.0-or-later	—	Details →
1.0.5-beta-tags.0	15 Dec 2021	none	AGPL-3.0-or-later	—	Details →
1.0.5-beta-protections-refactor.0	15 Dec 2021	none	AGPL-3.0-or-later	—	Details →
1.0.4	26 Oct 2021	none	AGPL-3.0-or-later	—	Details →
1.0.3	20 Oct 2021	none	AGPL-3.0-or-later	—	Details →
1.0.2	01 Oct 2021	none	AGPL-3.0-or-later	—	Details →
1.0.1	17 Sep 2021	none	AGPL-3.0-or-later	—	Details →
1.0.0	28 May 2021	none	AGPL-3.0-or-later	—	Details →

All 67 versions Vulert tracks for this package. 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.

Other ways into the data

03 Vulnerabilities

Recorded vulnerabilities for @standardnotes/time

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/time

Is @standardnotes/time safe to use?

Vulert has no vulnerabilities on record for @standardnotes/time 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/time's Vulert package health score?

Vulert scores @standardnotes/time 69/100, which reads as usable, but worth attention. 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/time affected?

No. 1.19.1, 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/time should I use?

1.19.1 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/time have?

0 vulnerabilities are recorded for @standardnotes/time 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/time vulnerabilities disclosed?

0 vulnerabilities were recorded for @standardnotes/time 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/time 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/time for upcoming vulnerabilities?

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