VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@accordproject/markdown-cli: vulnerability history, versions and safety

@accordproject/markdown-cli is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 120 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 25 Nov 2025.

See the disclosure history →
i
1 malicious-package vulnerabilities

A published version contained malicious code.

See malicious packages in npm →

See all @accordproject/markdown-cli vulnerabilities

Vulert verdict on @accordproject/markdown-cli 2.0.0 i

Updated on 23 Oct 2026

Malicious package: every vulnerability Vulert records for @accordproject/markdown-cli 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 Quiet

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.0 — affected i
  • Vulnerabilities on record 1 over 1 year · 1 in the last year i
  • Latest disclosure 25 Nov 2025 i
  • Highest CVSS n/a i
  • With no published fix 1 i
  • Malicious packages 1 i
  • Stars 86 i
  • OpenSSF scorecard 3/10 i
  • Last release this month i
  • Licence Apache-2.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 @accordproject/markdown-cli, 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.0 11 Oct 2026 C1 malicious Apache-2.0 No Details →
1.1.0 14 Sep 2026 C1 malicious Apache-2.0 No Details →
1.0.1 03 Jun 2026 C1 malicious Apache-2.0 No Details →
0.18.1 19 May 2026 C1 malicious Apache-2.0 No Details →
0.18.0 06 May 2026 C1 malicious Apache-2.0 No Details →
0.17.2 26 Feb 2026 C1 malicious Apache-2.0 No Details →
0.17.1 26 Feb 2026 C1 malicious Apache-2.0 No Details →
0.17.0 26 Feb 2026 C1 malicious Apache-2.0 No Details →
0.16.20-20251210135052 10 Dec 2025 C1 malicious Apache-2.0 No Details →
0.16.20-20251124101423 24 Nov 2025 C1 malicious Apache-2.0 No Details →
0.16.20-20250425131849 25 Apr 2025 C1 malicious Apache-2.0 No Details →
0.16.20-20241202053009 02 Dec 2024 C1 malicious Apache-2.0 No Details →
0.16.26 02 Dec 2024 C1 malicious Apache-2.0 No Details →
0.16.20-20241202052456 02 Dec 2024 C1 malicious Apache-2.0 No Details →
0.16.20-20241129151124 29 Nov 2024 C1 malicious Apache-2.0 No Details →
0.16.20-20241129142329 29 Nov 2024 C1 malicious Apache-2.0 No Details →
0.16.20-20241129105741 29 Nov 2024 C1 malicious Apache-2.0 No Details →
0.16.20-20241108141903 08 Nov 2024 C1 malicious Apache-2.0 No Details →
0.16.20-20241108140125 08 Nov 2024 C1 malicious Apache-2.0 No Details →
0.16.20-20241011154834 11 Oct 2024 C1 malicious Apache-2.0 No Details →
0.16.25 11 Oct 2024 C1 malicious Apache-2.0 No Details →
0.16.20-20241011154443 11 Oct 2024 C1 malicious Apache-2.0 No Details →
0.16.20-20240704185032 04 Jul 2024 C1 malicious Apache-2.0 No Details →
0.16.20-20240619132303 19 Jun 2024 C1 malicious Apache-2.0 No Details →
0.16.20-20240619132208 19 Jun 2024 C1 malicious Apache-2.0 No Details →
0.16.24 19 Jun 2024 C1 malicious Apache-2.0 No Details →
0.16.20-20240619124600 19 Jun 2024 C1 malicious Apache-2.0 No Details →
0.16.20-20240619123601 19 Jun 2024 C1 malicious Apache-2.0 No Details →
0.16.20-20240619121415 19 Jun 2024 C1 malicious Apache-2.0 No Details →
0.16.20-20240619121256 19 Jun 2024 C1 malicious Apache-2.0 No Details →
0.16.20-20240619115940 19 Jun 2024 C1 malicious Apache-2.0 No Details →
0.16.20-20240618152732 18 Jun 2024 C1 malicious Apache-2.0 No Details →
0.16.20-20240618152633 18 Jun 2024 C1 malicious Apache-2.0 No Details →
0.16.20-20240614162113 14 Jun 2024 C1 malicious Apache-2.0 No Details →
0.16.23 14 Jun 2024 C1 malicious Apache-2.0 No Details →
0.16.20-20240614133001 14 Jun 2024 C1 malicious Apache-2.0 No Details →
0.16.20-20240614131957 14 Jun 2024 C1 malicious Apache-2.0 No Details →
0.16.20-20240614123743 14 Jun 2024 C1 malicious Apache-2.0 No Details →
0.16.20-20240614121758 14 Jun 2024 C1 malicious Apache-2.0 No Details →
0.16.20-20240614121411 14 Jun 2024 C1 malicious Apache-2.0 No Details →
0.16.20-20240523100444 23 May 2024 C1 malicious Apache-2.0 No Details →
0.16.20-20240523100430 23 May 2024 C1 malicious Apache-2.0 No Details →
0.16.20-20240523094516 23 May 2024 C1 malicious Apache-2.0 No Details →
0.16.20-20240523094457 23 May 2024 C1 malicious Apache-2.0 No Details →
0.16.20-20240523094403 23 May 2024 C1 malicious Apache-2.0 No Details →
0.16.20-20240523094320 23 May 2024 C1 malicious Apache-2.0 No Details →
0.16.20-20240409224611 09 Apr 2024 C1 malicious Apache-2.0 No Details →
0.16.20-20240409220506 09 Apr 2024 C1 malicious Apache-2.0 No Details →
0.16.20-20240409215529 09 Apr 2024 C1 malicious Apache-2.0 No Details →
0.16.20-20240310170916 10 Mar 2024 C1 malicious Apache-2.0 No Details →
0.16.20-20231101111536 01 Nov 2023 C1 malicious Apache-2.0 No Details →
0.16.20-20231101105225 01 Nov 2023 C1 malicious Apache-2.0 No Details →
0.16.20-20231101105159 01 Nov 2023 C1 malicious Apache-2.0 No Details →
0.16.20-20231101105023 01 Nov 2023 C1 malicious Apache-2.0 No Details →
0.16.20-20231101104951 01 Nov 2023 C1 malicious Apache-2.0 No Details →
0.16.20-20231101104649 01 Nov 2023 C1 malicious Apache-2.0 No Details →
0.16.20-20231101104117 01 Nov 2023 C1 malicious Apache-2.0 No Details →
0.16.20-20231101104050 01 Nov 2023 C1 malicious Apache-2.0 No Details →
0.16.22 01 Nov 2023 C1 malicious Apache-2.0 No Details →
0.16.20-20230927134032 27 Sep 2023 C1 malicious Apache-2.0 No Details →
0.16.21 27 Sep 2023 C1 malicious Apache-2.0 No Details →
0.16.20-20230927120327 27 Sep 2023 C1 malicious Apache-2.0 No Details →
0.16.20-20230926152530 26 Sep 2023 C1 malicious Apache-2.0 No Details →
0.16.20-20230926144654 26 Sep 2023 C1 malicious Apache-2.0 No Details →
0.16.20-20230811084906 11 Aug 2023 C1 malicious Apache-2.0 No Details →
0.16.19 11 Aug 2023 C1 malicious Apache-2.0 No Details →
0.16.19-20230811083802 11 Aug 2023 C1 malicious Apache-2.0 No Details →
0.16.19-20230810171925 10 Aug 2023 C1 malicious Apache-2.0 No Details →
0.16.19-20230804115512 04 Aug 2023 C1 malicious Apache-2.0 No Details →
0.16.18 04 Aug 2023 C1 malicious Apache-2.0 No Details →
0.16.18-20230804111004 04 Aug 2023 C1 malicious Apache-2.0 No Details →
0.16.18-20230804110951 04 Aug 2023 C1 malicious Apache-2.0 No Details →
0.16.18-20230804110323 04 Aug 2023 C1 malicious Apache-2.0 No Details →
0.16.18-20230803154333 03 Aug 2023 C1 malicious Apache-2.0 No Details →
0.16.17 03 Aug 2023 C1 malicious Apache-2.0 No Details →
0.16.14-20230803151940 03 Aug 2023 C1 malicious Apache-2.0 No Details →
0.16.14-20230803151723 03 Aug 2023 C1 malicious Apache-2.0 No Details →
0.16.14-20230803143558 03 Aug 2023 C1 malicious Apache-2.0 No Details →
0.16.14-20230803135023 03 Aug 2023 C1 malicious Apache-2.0 No Details →
0.16.14-20230803134744 03 Aug 2023 C1 malicious Apache-2.0 No Details →
0.16.14-20230803134618 03 Aug 2023 C1 malicious Apache-2.0 No Details →
0.16.14-20230803134034 03 Aug 2023 C1 malicious Apache-2.0 No Details →
0.16.13 05 Jul 2023 C1 malicious Apache-2.0 No Details →
0.16.13-20230705112453 05 Jul 2023 C1 malicious Apache-2.0 No Details →
0.16.13-20230705112140 05 Jul 2023 C1 malicious Apache-2.0 No Details →
0.16.13-20230705111235 05 Jul 2023 C1 malicious Apache-2.0 No Details →
0.16.13-20230705110844 05 Jul 2023 C1 malicious Apache-2.0 No Details →
0.16.12-20230705110351 05 Jul 2023 C1 malicious Apache-2.0 No Details →
0.16.12-20230705110156 05 Jul 2023 C1 malicious Apache-2.0 No Details →
0.16.12 04 Jul 2023 C1 malicious Apache-2.0 No Details →
0.16.12-20230704141805 04 Jul 2023 C1 malicious Apache-2.0 No Details →
0.16.12-20230704141519 04 Jul 2023 C1 malicious Apache-2.0 No Details →
0.16.12-20230704135455 04 Jul 2023 C1 malicious Apache-2.0 No Details →
0.16.11 04 Jul 2023 C1 malicious Apache-2.0 No Details →
0.16.9-20230703204947 03 Jul 2023 C1 malicious Apache-2.0 No Details →
0.16.9-20230703183405 03 Jul 2023 C1 malicious Apache-2.0 No Details →
0.16.9-20230703163636 03 Jul 2023 C1 malicious Apache-2.0 No Details →
0.16.9-20230606221743 06 Jun 2023 C1 malicious Apache-2.0 No Details →
0.16.9-20230606221114 06 Jun 2023 C1 malicious Apache-2.0 No Details →
0.16.9-20230606215506 06 Jun 2023 C1 malicious Apache-2.0 No Details →
0.16.8 06 Jun 2023 C1 malicious — No Details →
0.16.8-20230606190720 06 Jun 2023 C1 malicious — No Details →
0.16.8-20230606190709 06 Jun 2023 C1 malicious — No Details →
0.16.8-20230606173743 06 Jun 2023 C1 malicious — No Details →
0.16.7 06 Jun 2023 C1 malicious — No Details →
0.16.6-20230606012610 06 Jun 2023 C1 malicious — No Details →
0.16.6-20230606011712 06 Jun 2023 C1 malicious — No Details →
0.16.6 06 Jun 2023 C1 malicious — No Details →
0.16.6-20230518154320 18 May 2023 C1 malicious — No Details →
0.16.6-20230518151605 18 May 2023 C1 malicious — No Details →
0.16.6-20230518151000 18 May 2023 C1 malicious — No Details →
0.16.6-20230518150341 18 May 2023 C1 malicious — No Details →
0.16.6-20230518145230 18 May 2023 C1 malicious — No Details →
0.16.6-20230516075233 16 May 2023 C1 malicious — No Details →
0.16.6-20230404144219 04 Apr 2023 C1 malicious — No Details →
0.16.6-20230317163634 17 Mar 2023 C1 malicious — No Details →
0.16.6-20230307230034 07 Mar 2023 C1 malicious — No Details →
0.16.6-20230307220310 07 Mar 2023 C1 malicious — No Details →
0.16.6-20230307202746 07 Mar 2023 C1 malicious — No Details →
0.16.6-20230307194712 07 Mar 2023 C1 malicious — No Details →

The newest 120 of 1,013 versions Vulert tracks. 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 @accordproject/markdown-cli

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical Malicious Code Vulnerability in @accordproject/markdown-cli Package N/A critical No fix published 25 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: 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 @accordproject/markdown-cli

Is @accordproject/markdown-cli safe to use?

No. Vulert records a malicious-package vulnerability for @accordproject/markdown-cli: 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 @accordproject/markdown-cli's Vulert package health score?

Vulert scores @accordproject/markdown-cli 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 @accordproject/markdown-cli affected?

Yes. 2.0.0, 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.

How many vulnerabilities does @accordproject/markdown-cli have?

1 vulnerability is recorded for @accordproject/markdown-cli 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 @accordproject/markdown-cli vulnerabilities disclosed?

1 vulnerability was recorded for @accordproject/markdown-cli in the last 12 months, and the oldest entry in this database dates to 25 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 @accordproject/markdown-cli 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 @accordproject/markdown-cli for upcoming vulnerabilities?

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