VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@theguild/remark-npm2yarn: vulnerability history, versions and safety

@theguild/remark-npm2yarn 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 @theguild/remark-npm2yarn vulnerabilities

Vulert verdict on @theguild/remark-npm2yarn 0.3.3 i

Updated on 23 Oct 2026

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

Package health score 79/100
  • Security No known security issues
  • Maintenance Maintaining
  • Popularity Niche
  • Community Not enough data

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

  • Current release 0.3.3 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 33 packages i
  • Last release 23 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 @theguild/remark-npm2yarn, 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
0.3.3 23 Oct 2024 none MIT — Details →
0.3.3-alpha-20241023143907-2e6aa0e934f3fe0664f78b5435ae77e924af8de9 23 Oct 2024 none MIT — Details →
0.3.2 01 Sep 2024 none MIT — Details →
0.3.2-alpha-20240831235520-235c11e37896deba4a3bfc34b7202e4b88c60a91 31 Aug 2024 none MIT — Details →
0.3.2-alpha-20240831235032-87454db4725861322ea8a48550b1308658793ccf 31 Aug 2024 none MIT — Details →
0.3.2-alpha-20240831233505-b3602142a2474d285107cb7048dbff3d5d8b5114 31 Aug 2024 none MIT — Details →
0.3.1 31 Aug 2024 none MIT — Details →
0.3.1-alpha-20240831094111-4b3e75194d119f0f8a8c62fcfbdcf1265ee1f294 31 Aug 2024 none MIT — Details →
0.3.1-alpha-20240829105018-3b815eccd858f12e7946337e4f3b721400c75c21 29 Aug 2024 none MIT — Details →
0.3.0 08 Oct 2023 none MIT — Details →
0.3.0-alpha-20231008200225-c530235 08 Oct 2023 none MIT — Details →
0.3.0-alpha-20231008193229-d88eb1b 08 Oct 2023 none MIT — Details →
0.3.0-alpha-20231008193103-9105398 08 Oct 2023 none MIT — Details →
0.3.0-alpha-20231008161714-aac4bf2 08 Oct 2023 none MIT — Details →
0.3.0-alpha-20231008120445-835bf94 08 Oct 2023 none MIT — Details →
0.3.0-alpha-20231008120456-8a73327 08 Oct 2023 none MIT — Details →
0.3.0-alpha-20231008091814-bb57f20 08 Oct 2023 none MIT — Details →
0.3.0-alpha-20231008091731-8191ffa 08 Oct 2023 none MIT — Details →
0.3.0-alpha-20231008071938-58b7620 08 Oct 2023 none MIT — Details →
0.3.0-alpha-20231008071908-48b0ba8 08 Oct 2023 none MIT — Details →
0.3.0-alpha-20231008041854-a1545b6 08 Oct 2023 none MIT — Details →
0.3.0-alpha-20231008041801-d9e7331 08 Oct 2023 none MIT — Details →
0.3.0-alpha-20231008033518-4975734 08 Oct 2023 none MIT — Details →
0.3.0-alpha-20231008031606-869b52b 08 Oct 2023 none MIT — Details →
0.3.0-alpha-20231008030941-b84d52a 08 Oct 2023 none MIT — Details →
0.3.0-alpha-20231008030857-6ed784f 08 Oct 2023 none MIT — Details →
0.3.0-alpha-20231008021715-15250c2 08 Oct 2023 none MIT — Details →
0.3.0-alpha-20231008020930-b87d318 08 Oct 2023 none MIT — Details →
0.3.0-alpha-20231008020834-1cf4b22 08 Oct 2023 none MIT — Details →
0.3.0-alpha-20231008020754-05d83b3 08 Oct 2023 none MIT — Details →
0.2.1 08 Oct 2023 none MIT — Details →
0.2.1-alpha-20231008004945-db47384 08 Oct 2023 none MIT — Details →
0.2.1-alpha-20231008004903-aa6b8aa 08 Oct 2023 none MIT — Details →
0.2.1-alpha-20231008004819-8f4e424 08 Oct 2023 none MIT — Details →
0.1.2-alpha-20231007234032-7946fa3 07 Oct 2023 none MIT — Details →
0.3.0-alpha-20231007232355-2b5ea30 07 Oct 2023 none MIT — Details →
0.2.0 24 Sep 2023 none MIT — Details →
0.2.0-alpha-20230924011821-52ee2bf 24 Sep 2023 none MIT — Details →
0.2.0-alpha-20230924011730-6695b05 24 Sep 2023 none MIT — Details →
0.2.0-alpha-20230923214830-5f6f43b 23 Sep 2023 none MIT — Details →
0.2.0-alpha-20230923214532-6ff5426 23 Sep 2023 none MIT — Details →
0.2.0-alpha-20230923214429-402f5b4 23 Sep 2023 none MIT — Details →
0.2.0-alpha-20230923214340-6bead43 23 Sep 2023 none MIT — Details →
0.2.0-alpha-20230923214240-c15d22c 23 Sep 2023 none MIT — Details →
0.2.0-alpha-20230923181731-c2b5460 23 Sep 2023 none MIT — Details →
0.2.0-alpha-20230923181546-34d8e19 23 Sep 2023 none MIT — Details →
0.2.0-alpha-20230923181410-cfd7916 23 Sep 2023 none MIT — Details →
0.2.0-alpha-20230923181335-1ff2e03 23 Sep 2023 none MIT — Details →
0.2.0-alpha-20230923181134-2363516 23 Sep 2023 none MIT — Details →
0.2.0-alpha-20230923180705-972de08 23 Sep 2023 none MIT — Details →
0.2.0-alpha-20230923180243-12128ad 23 Sep 2023 none MIT — Details →
0.2.0-alpha-20230923174317-720ff84 23 Sep 2023 none MIT — Details →
0.2.0-alpha-20230923173149-22bb901 23 Sep 2023 none MIT — Details →
0.2.0-alpha-20230904225308-5ba1c7b 04 Sep 2023 none MIT — Details →
0.1.1 13 Jul 2023 none MIT — Details →
0.1.1-alpha-20230713101905-e9aa29e 13 Jul 2023 none MIT — Details →
0.1.1-alpha-20230713100541-209d05b 13 Jul 2023 none MIT — Details →
0.1.1-alpha-20230713095436-5dde54b 13 Jul 2023 none MIT — Details →
0.1.1-alpha-20230713094034-7d6ca88 13 Jul 2023 none MIT — Details →
0.1.1-alpha-20230713093457-1e1a13a 13 Jul 2023 none MIT — Details →
0.1.1-alpha-20230710124133-ec2c8eb 10 Jul 2023 none MIT — Details →
0.1.0 09 Jul 2023 none MIT — Details →
0.1.0-alpha-20230709174554-6a35a55 09 Jul 2023 none MIT — Details →
0.1.0-alpha-20230709174442-be48fe3 09 Jul 2023 none MIT — Details →
0.1.0-alpha-20230709174346-0ce91c6 09 Jul 2023 none MIT — Details →
0.1.0-alpha-20230709174252-a6af25f 09 Jul 2023 none MIT — Details →
0.1.0-alpha-20230709173322-11741e3 09 Jul 2023 none MIT — Details →
0.1.0-alpha-20230709140537-cd5c5c0 09 Jul 2023 none MIT — Details →
0.1.0-alpha-20230709135745-398a65f 09 Jul 2023 none MIT — Details →
0.1.0-alpha-20230709134619-0b6786d 09 Jul 2023 none MIT — Details →
0.1.0-alpha-20230709125835-3fe7d8a 09 Jul 2023 none MIT — Details →
0.1.0-alpha-20230709125158-7e5291f 09 Jul 2023 none MIT — Details →
0.1.0-alpha-20230709124250-c89d6c9 09 Jul 2023 none MIT — Details →
0.0.2-alpha-20230707135638-3baa9f2 07 Jul 2023 none MIT — Details →
0.0.1-alpha-20230608121717-6db271a 08 Jun 2023 none MIT — Details →
0.0.1 08 Jun 2023 none MIT — Details →
0.0.1-alpha-20230607233605-9492b5e 07 Jun 2023 none MIT — Details →
0.0.1-alpha-20230607121628-31dc2d0 07 Jun 2023 none MIT — Details →
0.0.1-alpha-20230607114007-670f2e7 07 Jun 2023 none MIT — Details →
0.0.1-alpha-20230607010630-fcda00f 07 Jun 2023 none MIT — Details →
0.0.1-alpha-20230606231910-a7ca92f 06 Jun 2023 none MIT — Details →
0.0.1-alpha-20230606231808-9760930 06 Jun 2023 none MIT — Details →
0.0.1-alpha-20230606181205-240fa0e 06 Jun 2023 none MIT — Details →
0.0.1-alpha-20230606130812-cbe49ad 06 Jun 2023 none MIT — Details →
0.0.1-alpha-20230606122321-171cccf 06 Jun 2023 none MIT — Details →
0.0.1-alpha-20230606120704-afeee28 06 Jun 2023 none MIT — Details →
0.0.1-alpha-20230606000659-174e849 06 Jun 2023 none MIT — Details →
0.0.1-alpha-20230606000133-113c9fc 06 Jun 2023 none MIT — Details →

All 88 versions Vulert tracks for this package. 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 @theguild/remark-npm2yarn

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 @theguild/remark-npm2yarn

Is @theguild/remark-npm2yarn safe to use?

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

Vulert scores @theguild/remark-npm2yarn 79/100, which reads as in good shape. 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 @theguild/remark-npm2yarn affected?

No. 0.3.3, 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 @theguild/remark-npm2yarn should I use?

0.3.3 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 @theguild/remark-npm2yarn have?

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

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

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