Vulnerability Database · npm · Package report

@npmcli/run-script: vulnerability history, versions and safety

Q: How do I monitor @npmcli/run-script for upcoming vulnerabilities?

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

@npmcli/run-script is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.

0 vulnerabilities recorded

Nothing recorded for this package in the npm ecosystem.

0 with no fix published

Every vulnerability has a patched version to move to.

0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →

0 malicious-package vulnerabilities

No published version shipped hostile code.

See all @npmcli/run-script vulnerabilities

Vulert verdict on @npmcli/run-script 11.0.0 i

Updated on 23 Oct 2026

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

Package health score 76/100

Security Minor issues
Maintenance Sustainable
Popularity Niche
Community Quiet

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

Current release 11.0.0 — unaffected i
Vulnerabilities on record 0 i
Highest CVSS n/a i
With no published fix 0 i
Depended on by 325 packages i
Stars 60 i
OpenSSF scorecard 5/10 i
Last release 4 months ago i
Licence ISC 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.

Scan your app free →

01 Versions

Which versions are affected

Every version Vulert tracks for @npmcli/run-script, 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.

Version	Released	Vulert vulnerabilities	Licence	Fix published	Details
11.0.0	15 Jun 2026	none	ISC	—	Details →
10.0.4	26 Feb 2026	none	ISC	—	Details →
10.0.3	13 Nov 2025	none	ISC	—	Details →
10.0.2	24 Oct 2025	none	ISC	—	Details →
10.0.1	23 Oct 2025	none	ISC	—	Details →
10.0.0	02 Sep 2025	none	ISC	—	Details →
9.1.0	07 Mar 2025	none	ISC	—	Details →
9.0.2	04 Dec 2024	none	ISC	—	Details →
9.0.1	02 Oct 2024	none	ISC	—	Details →
9.0.0	26 Sep 2024	none	ISC	—	Details →
8.1.0	29 Apr 2024	none	ISC	—	Details →
8.0.0	12 Apr 2024	none	ISC	—	Details →
7.0.4	23 Jan 2024	none	ISC	—	Details →
7.0.3	04 Jan 2024	none	ISC	—	Details →
7.0.2	29 Oct 2023	none	ISC	—	Details →
7.0.1	30 Aug 2023	none	ISC	—	Details →
7.0.0	30 Aug 2023	none	ISC	—	Details →
6.0.2	08 May 2023	none	ISC	—	Details →
6.0.1	27 Apr 2023	none	ISC	—	Details →
6.0.0	02 Nov 2022	none	ISC	—	Details →
5.1.1	01 Nov 2022	none	ISC	—	Details →
5.1.0	01 Nov 2022	none	ISC	—	Details →
5.0.1	26 Oct 2022	none	ISC	—	Details →
5.0.0	14 Oct 2022	none	ISC	—	Details →
4.2.1	10 Aug 2022	none	ISC	—	Details →
4.2.0	01 Aug 2022	none	ISC	—	Details →
4.1.7	12 Jul 2022	none	ISC	—	Details →
4.1.6	12 Jul 2022	none	ISC	—	Details →
4.1.5	28 Jun 2022	none	ISC	—	Details →
4.1.4	27 Jun 2022	none	ISC	—	Details →
4.1.3	23 Jun 2022	none	ISC	—	Details →
4.1.2	22 Jun 2022	none	ISC	—	Details →
4.1.1	22 Jun 2022	none	ISC	—	Details →
4.1.0	21 Jun 2022	none	ISC	—	Details →
4.0.0	03 Jun 2022	none	ISC	—	Details →
3.0.3	25 May 2022	none	ISC	—	Details →
3.0.2	05 Apr 2022	none	ISC	—	Details →
3.0.1	02 Mar 2022	none	ISC	—	Details →
3.0.0	23 Feb 2022	none	ISC	—	Details →
2.0.0	27 Sep 2021	none	ISC	—	Details →
1.8.6	16 Aug 2021	none	ISC	—	Details →
1.8.5	22 Apr 2021	none	ISC	—	Details →
1.8.4	09 Mar 2021	none	ISC	—	Details →
1.8.3	10 Feb 2021	none	ISC	—	Details →
1.8.2	05 Feb 2021	none	ISC	—	Details →
1.8.1	23 Nov 2020	none	ISC	—	Details →
1.8.0	17 Nov 2020	none	ISC	—	Details →
1.7.5	06 Nov 2020	none	ISC	—	Details →
1.7.4	28 Oct 2020	none	ISC	—	Details →
1.7.3	27 Oct 2020	none	ISC	—	Details →
1.7.2	02 Oct 2020	none	ISC	—	Details →
1.7.1	02 Oct 2020	none	ISC	—	Details →
1.7.0	30 Sep 2020	none	ISC	—	Details →
1.6.0	22 Sep 2020	none	ISC	—	Details →
1.5.0	10 Aug 2020	none	ISC	—	Details →
1.4.0	30 Jul 2020	none	ISC	—	Details →
1.3.1	06 Apr 2020	none	ISC	—	Details →
1.3.0	09 Mar 2020	none	ISC	—	Details →
1.2.1	28 Jan 2020	none	ISC	—	Details →
1.2.0	28 Jan 2020	none	ISC	—	Details →
1.1.2	28 Jan 2020	none	ISC	—	Details →
1.1.1	28 Jan 2020	none	ISC	—	Details →
1.1.0	24 Jan 2020	none	ISC	—	Details →
1.0.1	22 Jan 2020	none	ISC	—	Details →
1.0.0	22 Jan 2020	none	ISC	—	Details →

All 65 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.

Other ways into the data

03 Vulnerabilities

Recorded vulnerabilities for @npmcli/run-script

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 @npmcli/run-script

Is @npmcli/run-script safe to use?

Vulert has no vulnerabilities on record for @npmcli/run-script 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 @npmcli/run-script's Vulert package health score?

Vulert scores @npmcli/run-script 76/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 @npmcli/run-script affected?

No. 11.0.0, 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 @npmcli/run-script should I use?

11.0.0 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 @npmcli/run-script have?

0 vulnerabilities are recorded for @npmcli/run-script 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 @npmcli/run-script vulnerabilities disclosed?

0 vulnerabilities were recorded for @npmcli/run-script 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 @npmcli/run-script 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 @npmcli/run-script for upcoming vulnerabilities?

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