Vulnerability Database · npm · Package report

@astrojs/markdown-remark: vulnerability history, versions and safety

@astrojs/markdown-remark 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 @astrojs/markdown-remark 7.3.4 i

Updated on 23 Oct 2026

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

Package health score 94/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Active

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

  • Current release 7.3.4 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 98 packages i
  • Stars 63,299 i
  • Last release this month 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 @astrojs/markdown-remark, 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
7.3.4 21 Oct 2026 none MIT — Details →
7.3.3 15 Oct 2026 none MIT — Details →
7.3.2 06 Oct 2026 none MIT — Details →
7.3.1 08 Sep 2026 none MIT — Details →
7.3.0 31 Aug 2026 none MIT — Details →
7.2.4 19 Aug 2026 none MIT — Details →
7.2.3 18 Aug 2026 none MIT — Details →
7.2.2 28 Jul 2026 none MIT — Details →
7.2.1 02 Jul 2026 none MIT — Details →
7.2.0 28 May 2026 none MIT — Details →
7.1.2 13 May 2026 none MIT — Details →
7.1.1 22 Apr 2026 none MIT — Details →
7.1.0 26 Mar 2026 none MIT — Details →
7.0.1 18 Mar 2026 none MIT — Details →
6.3.11 10 Mar 2026 none MIT — Details →
7.0.0 10 Mar 2026 none MIT — Details →
7.0.0-beta.11 06 Mar 2026 none MIT — Details →
7.0.0-beta.10 05 Mar 2026 none MIT — Details →
7.0.0-beta.9 04 Mar 2026 none MIT — Details →
7.0.0-beta.8 26 Feb 2026 none MIT — Details →
7.0.0-beta.7 17 Feb 2026 none MIT — Details →
7.0.0-beta.6 09 Feb 2026 none MIT — Details →
7.0.0-beta.5 05 Feb 2026 none MIT — Details →
7.0.0-beta.4 04 Feb 2026 none MIT — Details →
7.0.0-beta.3 30 Jan 2026 none MIT — Details →
7.0.0-beta.2 23 Jan 2026 none MIT — Details →
7.0.0-beta.1 13 Jan 2026 none MIT — Details →
6.3.10 10 Dec 2025 none MIT — Details →
6.3.9 17 Nov 2025 none MIT — Details →
7.0.0-alpha.0 10 Nov 2025 none MIT — Details →
6.3.8 09 Oct 2025 none MIT — Details →
6.3.7 22 Sep 2025 none MIT — Details →
6.3.6 15 Aug 2025 none MIT — Details →
6.3.5 01 Aug 2025 none MIT — Details →
6.3.4 31 Jul 2025 none MIT — Details →
6.3.3 17 Jul 2025 none MIT — Details →
6.3.2 22 May 2025 none MIT — Details →
6.3.1 18 Mar 2025 none MIT — Details →
6.3.0 13 Mar 2025 none MIT — Details →
6.2.1 11 Mar 2025 none MIT — Details →
6.2.0 27 Feb 2025 none MIT — Details →
6.1.0 30 Jan 2025 none MIT — Details →
0.0.0-router-noexec-20250129135648 29 Jan 2025 none MIT — Details →
6.0.2 15 Jan 2025 none MIT — Details →
0.0.0-middleware-fix-20241210163342 10 Dec 2024 none MIT — Details →
6.0.1 09 Dec 2024 none MIT — Details →
0.0.0-routemanifest-refactor-20241209145150 09 Dec 2024 none MIT — Details →
0.0.0-svg-leak-20241209134543 09 Dec 2024 none MIT — Details →
0.0.0-astroenv-dev-20241206160513 06 Dec 2024 none MIT — Details →
0.0.0-process-env-override-20241206130809 06 Dec 2024 none MIT — Details →
0.0.0-sessions-20241205174618 05 Dec 2024 none MIT — Details →
0.0.0-sessions-20241205172911 05 Dec 2024 none MIT — Details →
0.0.0-sessions-20241205163205 05 Dec 2024 none MIT — Details →
0.0.0-sessions-20241205161456 05 Dec 2024 none MIT — Details →
0.0.0-sessions-20241205160628 05 Dec 2024 none MIT — Details →
6.0.0 03 Dec 2024 none MIT — Details →
0.0.0-sessions-20241128172109 28 Nov 2024 none MIT — Details →
0.0.0-sessions-20241128161723 28 Nov 2024 none MIT — Details →
0.0.0-sessions-20241128134018 28 Nov 2024 none MIT — Details →
0.0.0-sessions-20241128091859 28 Nov 2024 none MIT — Details →
6.0.0-beta.3 27 Nov 2024 none MIT — Details →
0.0.0-sessions-20241127112400 27 Nov 2024 none MIT — Details →
0.0.0-sessions-20241125115314 25 Nov 2024 none MIT — Details →
0.0.0-sessions-20241125113325 25 Nov 2024 none MIT — Details →
0.0.0-sessions-20241122143330 22 Nov 2024 none MIT — Details →
0.0.0-sessions-20241122114539 22 Nov 2024 none MIT — Details →
5.3.0 10 Oct 2024 none MIT — Details →
6.0.0-beta.2 01 Oct 2024 none MIT — Details →
6.0.0-beta.1 17 Sep 2024 none MIT — Details →
6.0.0-alpha.1 03 Sep 2024 none MIT — Details →
6.0.0-alpha.0 19 Aug 2024 none MIT — Details →
5.2.0 18 Jul 2024 none MIT — Details →
0.0.0-server-islands-20240718131003 18 Jul 2024 none MIT — Details →
0.0.0-server-islands-20240718105514 18 Jul 2024 none MIT — Details →
0.0.0-server-islands-20240718103853 18 Jul 2024 none MIT — Details →
0.0.0-noSync-20240718092432 18 Jul 2024 none MIT — Details →
0.0.0-server-islands-20240709194928 09 Jul 2024 none MIT — Details →
0.0.0-server-islands-20240703133809 03 Jul 2024 none MIT — Details →
5.1.1 24 Jun 2024 none MIT — Details →
0.0.0-server-islands-20240621194657 21 Jun 2024 none MIT — Details →
5.1.0 11 Apr 2024 none MIT — Details →
0.0.0-10745-20240410180016 10 Apr 2024 none MIT — Details →
5.0.0 02 Apr 2024 none MIT — Details →
4.3.2 26 Mar 2024 none MIT — Details →
4.3.1 20 Mar 2024 none MIT — Details →
4.3.0 11 Mar 2024 none MIT — Details →
0.0.0-non-admin-test-20240308195029 08 Mar 2024 none MIT — Details →
4.2.1 30 Jan 2024 none MIT — Details →
4.2.0 22 Jan 2024 none MIT — Details →
4.1.0 18 Jan 2024 none MIT — Details →
4.0.1 11 Dec 2023 none MIT — Details →
0.0.0-add-stable-20231208215901 08 Dec 2023 none MIT — Details →
4.0.0 05 Dec 2023 none MIT — Details →
4.0.0-beta.0 27 Nov 2023 none MIT — Details →
3.5.0 14 Nov 2023 none MIT — Details →
3.4.0 09 Nov 2023 none MIT — Details →
0.0.0-assets-uint8array-20231109073138 09 Nov 2023 none MIT — Details →
0.0.0-content-cache-20231108193031 08 Nov 2023 none MIT — Details →
3.3.0 12 Oct 2023 none MIT — Details →
3.2.1 05 Oct 2023 none MIT — Details →
3.2.0 14 Sep 2023 none — — Details →
3.1.0 08 Sep 2023 none — — Details →
0.0.0-perf-20230907211643 07 Sep 2023 none — — Details →
0.0.0-perf-20230907211008 07 Sep 2023 none — — Details →
0.0.0-propagation-metadata-20230907174633 07 Sep 2023 none — — Details →
0.0.0-propagation-metadata-20230907173002 07 Sep 2023 none — — Details →
3.0.0 30 Aug 2023 none — — Details →
3.0.0-rc.1 22 Aug 2023 none — — Details →
3.0.0-beta.0 03 Aug 2023 none — — Details →
2.2.1 18 May 2023 none — — Details →
2.2.0 04 May 2023 none — — Details →
0.0.0-middleware-20230418135507 18 Apr 2023 none — — Details →
2.1.4 13 Apr 2023 none — — Details →
2.1.3 05 Apr 2023 none — — Details →
0.0.0-middleware-20230405160200 05 Apr 2023 none — — Details →
0.0.0-head-prop-20230323183456 23 Mar 2023 none — — Details →
2.1.2 22 Mar 2023 none — — Details →
2.1.1 21 Mar 2023 none — — Details →
2.1.0 07 Mar 2023 none — — Details →
0.0.0-experimental-assets-20230307131344 07 Mar 2023 none — — Details →

The newest 120 of 190 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 @astrojs/markdown-remark

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 @astrojs/markdown-remark

Is @astrojs/markdown-remark safe to use?

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

Vulert scores @astrojs/markdown-remark 94/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 @astrojs/markdown-remark affected?

No. 7.3.4, 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.

How many vulnerabilities does @astrojs/markdown-remark have?

0 vulnerabilities are recorded for @astrojs/markdown-remark 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 @astrojs/markdown-remark vulnerabilities disclosed?

0 vulnerabilities were recorded for @astrojs/markdown-remark 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 @astrojs/markdown-remark 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 @astrojs/markdown-remark for upcoming vulnerabilities?

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