VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

posthog-docusaurus: vulnerability history, versions and safety

posthog-docusaurus is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 11 releases, first recorded in Nov 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded C1
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
1 in the last 12 months

Most recent disclosure 24 Nov 2025.

See the disclosure history →
i
1 malicious-package vulnerabilities

A published version contained malicious code.

See malicious packages in npm →

See all posthog-docusaurus vulnerabilities

Vulert verdict on posthog-docusaurus 2.0.5 i

Updated on 22 Oct 2026

Malicious package: every vulnerability Vulert records for posthog-docusaurus is a malicious-package vulnerability — a published version contained hostile code rather than a bug. Do not install it, and check whether it is already resolved in your dependencies.

Package health score 15/100
  • Security Malicious code published
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Not enough data

The current release contains malicious code, which caps this score.

What to do: Do not install this package. If it is already in your dependency tree, remove or replace it, and check what resolved it in the first place. Vulert keeps watching the name: if a maintained replacement appears, you will see it here. Monitor it with Vulert →

  • Current release 2.0.5 — affected i
  • Vulnerabilities on record 1 over 1 year · 1 in the last year i
  • Latest disclosure 24 Nov 2025 i
  • Highest CVSS n/a i
  • With no published fix 1 i
  • Malicious packages 1 i
  • Last release 12 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 posthog-docusaurus, 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.0.5 10 Oct 2025 C1 malicious MIT No Details →
2.0.4 18 Mar 2025 C1 malicious MIT No Details →
2.0.2 10 Dec 2024 C1 malicious MIT No Details →
2.0.1 22 Jul 2024 C1 malicious MIT No Details →
2.0.0 12 Oct 2022 C1 malicious MIT No Details →
1.0.5 11 Oct 2022 C1 malicious MIT No Details →
1.0.4 03 Oct 2022 C1 malicious MIT No Details →
1.0.3 19 Jun 2020 C1 malicious MIT No Details →
1.0.2 19 Jun 2020 C1 malicious MIT No Details →
1.0.1 19 Jun 2020 C1 malicious MIT No Details →
1.0.0 18 Jun 2020 C1 malicious MIT No Details →

All 11 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 1 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for posthog-docusaurus

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Malicious Code Detected in posthog-docusaurus Package - Critical Vulnerability Alert N/A critical No fix published 24 Nov 2025

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

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 posthog-docusaurus

Is posthog-docusaurus safe to use?

No. Vulert records a malicious-package vulnerability for posthog-docusaurus: a published version contained hostile code rather than a bug, and the package looks like one that was withdrawn for abuse. Do not install it, and check whether it is already resolved in your dependencies.

What is posthog-docusaurus's Vulert package health score?

Vulert scores posthog-docusaurus 15/100, which reads as critical. 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). The current release contains malicious code, which caps this score.

Is the latest version of posthog-docusaurus affected?

Yes. 2.0.5, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of posthog-docusaurus should I use?

2.0.5 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 posthog-docusaurus have?

1 vulnerability is recorded for posthog-docusaurus in the npm ecosystem: 1 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 posthog-docusaurus vulnerabilities disclosed?

1 vulnerability was recorded for posthog-docusaurus in the last 12 months, and the oldest entry in this database dates to 24 Nov 2025. 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 posthog-docusaurus 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.

What does a malicious-package vulnerability mean?

It means the published package itself contained hostile code — a backdoor, a credential stealer or similar — rather than only a bug. Registries remove such packages once they are confirmed, so treat any application that resolved an affected version as compromised and rotate the credentials it could reach.

How do I monitor posthog-docusaurus for upcoming vulnerabilities?

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