VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@docusaurus/utils-common: vulnerability history, versions and safety

@docusaurus/utils-common 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 @docusaurus/utils-common vulnerabilities

Vulert verdict on @docusaurus/utils-common 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 88/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • 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 210 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/utils-common, 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-6989 23 Oct 2026 none MIT — Details →
4.0.0-canary-6988 23 Oct 2026 none MIT — Details →
4.0.0-canary-6987 23 Oct 2026 none MIT — Details →
4.0.0-canary-6986 23 Oct 2026 none MIT — Details →
4.0.0-canary-6985 16 Oct 2026 none MIT — Details →
4.0.0-canary-6983 16 Oct 2026 none MIT — Details →
4.0.0-canary-6980 16 Oct 2026 none MIT — Details →
4.0.0-canary-6979 16 Oct 2026 none MIT — Details →
4.0.0-canary-6977 16 Oct 2026 none MIT — Details →
4.0.0-canary-6978 16 Oct 2026 none MIT — Details →
4.0.0-canary-6976 16 Oct 2026 none MIT — Details →
4.0.0-canary-6975 16 Oct 2026 none MIT — Details →
4.0.0-canary-6974 16 Oct 2026 none MIT — Details →
4.0.0-canary-6973 16 Oct 2026 none MIT — Details →
4.0.0-canary-6972 16 Oct 2026 none MIT — Details →
4.0.0-canary-6971 16 Oct 2026 none MIT — Details →
4.0.0-canary-6970 16 Oct 2026 none MIT — Details →
4.0.0-canary-6969 16 Oct 2026 none MIT — Details →
4.0.0-canary-6968 16 Oct 2026 none MIT — Details →
4.0.0-canary-6967 16 Oct 2026 none MIT — Details →
4.0.0-canary-6966 16 Oct 2026 none MIT — Details →
4.0.0-canary-6965 16 Oct 2026 none MIT — Details →
4.0.0-canary-6964 16 Oct 2026 none MIT — Details →
4.0.0-canary-6963 16 Oct 2026 none MIT — Details →
4.0.0-canary-6961 16 Oct 2026 none MIT — Details →
4.0.0-canary-6960 16 Oct 2026 none MIT — Details →
4.0.0-canary-6959 16 Oct 2026 none MIT — Details →
4.0.0-canary-6958 16 Oct 2026 none MIT — Details →
4.0.0-canary-6956 16 Oct 2026 none MIT — Details →
4.0.0-canary-6953 16 Oct 2026 none MIT — Details →
4.0.0-canary-6952 16 Oct 2026 none MIT — Details →
4.0.0-canary-6951 16 Oct 2026 none MIT — Details →
4.0.0-canary-6948 16 Oct 2026 none MIT — Details →
4.0.0-canary-6947 16 Oct 2026 none MIT — Details →
4.0.0-canary-6946 16 Oct 2026 none MIT — Details →
4.0.0-canary-6945 16 Oct 2026 none MIT — Details →
4.0.0-canary-6944 16 Oct 2026 none MIT — Details →
4.0.0-canary-6943 16 Oct 2026 none MIT — Details →
4.0.0-canary-6942 16 Oct 2026 none MIT — Details →
4.0.0-canary-6941 16 Oct 2026 none MIT — Details →
4.0.0-canary-6939 16 Oct 2026 none MIT — Details →
4.0.0-canary-6938 16 Oct 2026 none MIT — Details →
4.0.0-canary-6937 15 Oct 2026 none MIT — Details →
4.0.0-canary-6936 15 Oct 2026 none MIT — Details →
4.0.0-canary-6935 15 Oct 2026 none MIT — Details →
4.0.0-canary-6930 15 Oct 2026 none MIT — Details →
4.0.0-canary-6929 15 Oct 2026 none MIT — Details →
4.0.0-canary-6928 15 Oct 2026 none MIT — Details →
4.0.0-canary-6927 15 Oct 2026 none MIT — Details →
4.0.0-canary-6925 15 Oct 2026 none MIT — Details →
4.0.0-canary-6924 15 Oct 2026 none MIT — Details →
4.0.0-canary-6923 15 Oct 2026 none MIT — Details →
4.0.0-canary-6922 15 Oct 2026 none MIT — Details →
4.0.0-canary-6920 15 Oct 2026 none MIT — Details →
4.0.0-canary-6918 15 Oct 2026 none MIT — Details →
4.0.0-canary-6917 15 Oct 2026 none MIT — Details →
4.0.0-canary-6913 09 Oct 2026 none MIT — Details →
4.0.0-canary-6912 09 Oct 2026 none MIT — Details →
4.0.0-canary-6911 09 Oct 2026 none MIT — Details →
4.0.0-canary-6909 09 Oct 2026 none MIT — Details →
4.0.0-canary-6907 09 Oct 2026 none MIT — Details →
4.0.0-canary-6905 09 Oct 2026 none MIT — 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-6868 01 Oct 2026 none MIT — Details →
4.0.0-canary-6869 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-6864 01 Oct 2026 none MIT — Details →
4.0.0-canary-6862 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 — — Details →
4.0.0-canary-6845 25 Sep 2026 none — — Details →
4.0.0-canary-6844 25 Sep 2026 none — — Details →
4.0.0-canary-6843 25 Sep 2026 none — — Details →
4.0.0-canary-6842 25 Sep 2026 none — — Details →
4.0.0-canary-6841 25 Sep 2026 none — — Details →
4.0.0-canary-6840 25 Sep 2026 none — — Details →
4.0.0-canary-6839 24 Sep 2026 none — — Details →
4.0.0-canary-6836 24 Sep 2026 none — — Details →
4.0.0-canary-6835 24 Sep 2026 none — — Details →
4.0.0-canary-6834 24 Sep 2026 none — — Details →
4.0.0-canary-6833 24 Sep 2026 none — — Details →
4.0.0-canary-6832 24 Sep 2026 none — — Details →
4.0.0-canary-6831 24 Sep 2026 none — — Details →
4.0.0-canary-6830 24 Sep 2026 none — — Details →
4.0.0-canary-6829 24 Sep 2026 none — — Details →
4.0.0-canary-6828 24 Sep 2026 none — — Details →
4.0.0-canary-6822 18 Sep 2026 none — — Details →
4.0.0-canary-6821 18 Sep 2026 none — — Details →
4.0.0-canary-6820 18 Sep 2026 none — — Details →

The newest 120 of 1,889 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/utils-common

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/utils-common

Is @docusaurus/utils-common safe to use?

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

Vulert scores @docusaurus/utils-common 88/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/utils-common 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/utils-common 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/utils-common have?

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

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

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