Vulnerability Database · npm · Package report

@docusaurus/faster: vulnerability history, versions and safety

@docusaurus/faster 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.

Vulert verdict on @docusaurus/faster 3.10.2 i

Updated on 23 Oct 2026

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

Package health score 86/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 3.10.2 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 11 packages i
  • Stars 66,550 i
  • OpenSSF scorecard 5/10 i
  • Last release 3 months ago i
  • Licence MIT 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 @docusaurus/faster, 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
4.0.0-canary-6904 09 Oct 2026 none MIT — Details →
4.0.0-canary-6903 09 Oct 2026 none MIT — Details →
4.0.0-canary-6902 09 Oct 2026 none MIT — Details →
4.0.0-canary-6901 09 Oct 2026 none MIT — Details →
4.0.0-canary-6899 09 Oct 2026 none MIT — Details →
4.0.0-canary-6898 09 Oct 2026 none MIT — Details →
4.0.0-canary-6896 09 Oct 2026 none MIT — Details →
4.0.0-canary-6894 09 Oct 2026 none MIT — Details →
4.0.0-canary-6893 09 Oct 2026 none MIT — Details →
4.0.0-canary-6892 09 Oct 2026 none MIT — Details →
4.0.0-canary-6891 09 Oct 2026 none MIT — Details →
4.0.0-canary-6888 09 Oct 2026 none MIT — Details →
4.0.0-canary-6885 09 Oct 2026 none MIT — Details →
4.0.0-canary-6884 08 Oct 2026 none MIT — Details →
4.0.0-canary-6883 05 Oct 2026 none MIT — Details →
4.0.0-canary-6882 02 Oct 2026 none MIT — Details →
4.0.0-canary-6881 02 Oct 2026 none MIT — Details →
4.0.0-canary-6880 02 Oct 2026 none MIT — Details →
4.0.0-canary-6879 02 Oct 2026 none MIT — Details →
4.0.0-canary-6877 02 Oct 2026 none MIT — Details →
4.0.0-canary-6875 02 Oct 2026 none MIT — Details →
4.0.0-canary-6874 01 Oct 2026 none MIT — Details →
4.0.0-canary-6873 01 Oct 2026 none MIT — Details →
4.0.0-canary-6872 01 Oct 2026 none MIT — Details →
4.0.0-canary-6870 01 Oct 2026 none MIT — Details →
4.0.0-canary-6869 01 Oct 2026 none MIT — Details →
4.0.0-canary-6868 01 Oct 2026 none MIT — Details →
4.0.0-canary-6866 01 Oct 2026 none MIT — Details →
4.0.0-canary-6865 01 Oct 2026 none MIT — Details →
4.0.0-canary-6863 01 Oct 2026 none MIT — Details →
4.0.0-canary-6862 01 Oct 2026 none MIT — Details →
4.0.0-canary-6860 01 Oct 2026 none MIT — Details →
4.0.0-canary-6861 01 Oct 2026 none MIT — Details →
4.0.0-canary-6859 01 Oct 2026 none MIT — Details →
4.0.0-canary-6858 01 Oct 2026 none MIT — Details →
4.0.0-canary-6855 01 Oct 2026 none MIT — Details →
4.0.0-canary-6853 01 Oct 2026 none MIT — Details →
4.0.0-canary-6852 01 Oct 2026 none MIT — Details →
4.0.0-canary-6848 25 Sep 2026 none MIT — Details →
4.0.0-canary-6845 25 Sep 2026 none MIT — Details →
4.0.0-canary-6844 25 Sep 2026 none MIT — Details →
4.0.0-canary-6843 25 Sep 2026 none MIT — Details →
4.0.0-canary-6842 25 Sep 2026 none MIT — Details →
4.0.0-canary-6841 25 Sep 2026 none MIT — Details →
4.0.0-canary-6840 25 Sep 2026 none MIT — Details →
4.0.0-canary-6839 24 Sep 2026 none MIT — Details →
4.0.0-canary-6836 24 Sep 2026 none MIT — Details →
4.0.0-canary-6835 24 Sep 2026 none MIT — Details →
4.0.0-canary-6834 24 Sep 2026 none MIT — Details →
4.0.0-canary-6833 24 Sep 2026 none MIT — Details →
4.0.0-canary-6832 24 Sep 2026 none MIT — Details →
4.0.0-canary-6831 24 Sep 2026 none MIT — Details →
4.0.0-canary-6830 24 Sep 2026 none MIT — Details →
4.0.0-canary-6829 24 Sep 2026 none MIT — Details →
4.0.0-canary-6828 24 Sep 2026 none MIT — Details →
4.0.0-canary-6822 18 Sep 2026 none MIT — Details →
4.0.0-canary-6821 18 Sep 2026 none MIT — Details →
4.0.0-canary-6820 18 Sep 2026 none MIT — Details →
4.0.0-canary-6818 18 Sep 2026 none MIT — Details →
4.0.0-canary-6817 18 Sep 2026 none MIT — Details →
4.0.0-canary-6816 18 Sep 2026 none MIT — Details →
4.0.0-canary-6815 18 Sep 2026 none MIT — Details →
4.0.0-canary-6814 17 Sep 2026 none MIT — Details →
4.0.0-canary-6813 17 Sep 2026 none MIT — Details →
4.0.0-canary-6811 17 Sep 2026 none MIT — Details →
4.0.0-canary-6810 17 Sep 2026 none MIT — Details →
4.0.0-canary-6809 17 Sep 2026 none MIT — Details →
4.0.0-canary-6808 14 Sep 2026 none MIT — Details →
3.10.1-canary-6807 14 Sep 2026 none MIT — Details →
3.10.1-canary-6805 14 Sep 2026 none MIT — Details →
3.10.1-canary-6800 11 Sep 2026 none MIT — Details →
3.10.1-canary-6803 10 Sep 2026 none MIT — Details →
3.10.2 10 Jul 2026 none MIT — Details →
3.10.1-canary-6655 04 Jun 2026 none MIT — Details →
3.10.1-canary-6654 04 Jun 2026 none MIT — Details →
3.10.1-canary-6653 02 Jun 2026 none MIT — Details →
3.10.1-canary-6652 02 Jun 2026 none MIT — Details →
3.10.1-canary-6651 01 Jun 2026 none MIT — Details →
3.10.1-canary-6650 01 Jun 2026 none MIT — Details →
3.10.1-canary-6649 01 Jun 2026 none MIT — Details →
3.10.1-canary-6648 01 Jun 2026 none MIT — Details →
3.10.1-canary-6647 01 Jun 2026 none MIT — Details →
3.10.1-canary-6646 29 May 2026 none MIT — Details →
3.10.1-canary-6645 29 May 2026 none MIT — Details →
3.10.1-canary-6644 29 May 2026 none MIT — Details →
3.10.1-canary-6643 29 May 2026 none MIT — Details →
3.10.1-canary-6642 29 May 2026 none MIT — Details →
3.10.1-canary-6641 29 May 2026 none MIT — Details →
3.10.1-canary-6640 28 May 2026 none MIT — Details →
3.10.1-canary-6639 28 May 2026 none MIT — Details →
3.10.1-canary-6638 28 May 2026 none MIT — Details →
3.10.1-canary-6636 28 May 2026 none MIT — Details →
3.10.1-canary-6635 28 May 2026 none MIT — Details →
3.10.1-canary-6632 22 May 2026 none MIT — Details →
3.10.1-canary-6631 22 May 2026 none MIT — Details →
3.10.1-canary-6630 22 May 2026 none MIT — Details →
3.10.1-canary-6628 22 May 2026 none MIT — Details →
3.10.1-canary-6627 22 May 2026 none MIT — Details →
3.10.1-canary-6624 21 May 2026 none MIT — Details →
3.10.1-canary-6622 21 May 2026 none MIT — Details →
3.10.1-canary-6621 21 May 2026 none — — Details →
3.10.1-canary-6618 21 May 2026 none — — Details →
3.10.1-canary-6616 21 May 2026 none — — Details →
3.10.1-canary-6615 21 May 2026 none — — Details →
3.10.1-canary-6612 15 May 2026 none — — Details →
3.10.1-canary-6611 15 May 2026 none — — Details →
3.10.1-canary-6610 15 May 2026 none — — Details →
3.10.1-canary-6609 15 May 2026 none — — Details →
3.10.1-canary-6608 14 May 2026 none — — Details →
3.10.1-canary-6604 09 May 2026 none — — Details →
3.10.1-canary-6603 09 May 2026 none — — Details →
3.10.1-canary-6597 08 May 2026 none — — Details →
3.10.1-canary-6596 07 May 2026 none — — Details →
3.10.1-canary-6593 07 May 2026 none — — Details →
3.10.1-canary-6591 30 Apr 2026 none — — Details →
3.9.2-canary-6589 30 Apr 2026 none — — Details →
3.10.1 30 Apr 2026 none — — Details →
3.9.2-canary-6567 30 Apr 2026 none — — Details →
3.9.2-canary-6566 30 Apr 2026 none — — Details →
3.9.2-canary-6588 30 Apr 2026 none — — Details →

The newest 120 of 437 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 @docusaurus/faster

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 @docusaurus/faster

Is @docusaurus/faster safe to use?

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

Vulert scores @docusaurus/faster 86/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 @docusaurus/faster affected?

No. 3.10.2, 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 @docusaurus/faster should I use?

3.10.2 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 @docusaurus/faster have?

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

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

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