VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

ng-packagr: vulnerability history, versions and safety

ng-packagr is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 0 release, first recorded in May 2021. 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 M1
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 ng-packagr vulnerabilities

Vulert verdict on ng-packagr 22.2.4 i

Updated on 23 Oct 2026

Good news: 22.2.4, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 1.

Package health score 80/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

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

  • Current release 22.2.4 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 07 May 2021 i
  • Highest CVSS 6.6 i
  • With no published fix 0 i
  • Depended on by 3 packages i
  • Stars 1,854 i
  • OpenSSF scorecard 5/10 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 ng-packagr, 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
22.3.0-next.2 01 Oct 2026 none MIT — Details →
22.2.4 01 Oct 2026 none MIT — Details →
22.2.3 30 Sep 2026 none MIT — Details →
22.2.2 28 Sep 2026 none MIT — Details →
22.2.1 23 Sep 2026 none MIT — Details →
22.3.0-next.1 23 Sep 2026 none MIT — Details →
22.2.0 23 Sep 2026 none MIT — Details →
22.3.0-next.0 23 Sep 2026 none MIT — Details →
22.2.0-rc.0 16 Sep 2026 none MIT — Details →
22.2.0-next.6 10 Sep 2026 none MIT — Details →
22.2.0-next.5 02 Sep 2026 none MIT — Details →
22.2.0-next.4 26 Aug 2026 none MIT — Details →
22.2.0-next.3 14 Aug 2026 none MIT — Details →
21.2.7 04 Aug 2026 none MIT — Details →
22.1.1 04 Aug 2026 none MIT — Details →
21.2.6 31 Jul 2026 none MIT — Details →
22.2.0-next.2 29 Jul 2026 none MIT — Details →
22.2.0-next.1 29 Jul 2026 none MIT — Details →
22.2.0-next.0 29 Jul 2026 none MIT — Details →
22.1.0 29 Jul 2026 none MIT — Details →
22.0.2 24 Jul 2026 none MIT — Details →
22.1.0-rc.0 24 Jul 2026 none MIT — Details →
22.1.0-next.4 24 Jul 2026 none MIT — Details →
22.1.0-next.3 01 Jul 2026 none MIT — Details →
22.0.1 01 Jul 2026 none MIT — Details →
22.1.0-next.2 11 Jun 2026 none MIT — Details →
22.1.0-next.1 03 Jun 2026 none MIT — Details →
22.0.0 03 Jun 2026 none MIT — Details →
22.1.0-next.0 03 Jun 2026 none MIT — Details →
21.2.5 02 Jun 2026 none MIT — Details →
22.0.0-rc.0 18 May 2026 none MIT — Details →
22.0.0-next.5 18 May 2026 none MIT — Details →
22.0.0-next.4 07 May 2026 none MIT — Details →
22.0.0-next.3 17 Apr 2026 none MIT — Details →
21.2.3 17 Apr 2026 none MIT — Details →
21.2.2 27 Mar 2026 none MIT — Details →
22.0.0-next.1 19 Mar 2026 none MIT — Details →
21.2.1 19 Mar 2026 none MIT — Details →
22.0.0-next.0 25 Feb 2026 none MIT — Details →
21.2.0 25 Feb 2026 none MIT — Details →
21.1.0 14 Jan 2026 none MIT — Details →
21.2.0-next.0 14 Jan 2026 none MIT — Details →
21.1.0-rc.0 07 Jan 2026 none MIT — Details →
21.0.1 15 Dec 2025 none MIT — Details →
21.0.0 19 Nov 2025 none MIT — Details →
21.1.0-next.0 19 Nov 2025 none MIT — Details →
20.3.2 13 Nov 2025 none MIT — Details →
20.3.1 12 Nov 2025 none MIT — Details →
21.0.0-rc.1 12 Nov 2025 none MIT — Details →
21.0.0-rc.0 29 Oct 2025 none MIT — Details →
21.0.0-next.4 01 Oct 2025 none MIT — Details →
21.0.0-next.3 22 Sep 2025 none MIT — Details →
21.0.0-next.2 22 Sep 2025 none MIT — Details →
21.0.0-next.1 22 Sep 2025 none MIT — Details →
20.3.0 10 Sep 2025 none MIT — Details →
21.0.0-next.0 20 Aug 2025 none MIT — Details →
20.2.0 20 Aug 2025 none MIT — Details →
20.2.0-rc.0 13 Aug 2025 none MIT — Details →
20.2.0-next.1 01 Aug 2025 none MIT — Details →
20.2.0-next.0 16 Jul 2025 none MIT — Details →
20.1.0 09 Jul 2025 none MIT — Details →
20.1.0-rc.0 01 Jul 2025 none MIT — Details →
20.0.1 18 Jun 2025 none MIT — Details →
20.1.0-next.0 28 May 2025 none MIT — Details →
20.0.0 28 May 2025 none MIT — Details →
20.0.0-rc.2 27 May 2025 none MIT — Details →
20.0.0-rc.1 21 May 2025 none MIT — Details →
20.0.0-rc.0 30 Apr 2025 none MIT — Details →
20.0.0-next.8 23 Apr 2025 none MIT — Details →
20.0.0-next.7 23 Apr 2025 none MIT — Details →
20.0.0-next.6 09 Apr 2025 none MIT — Details →
19.2.2 09 Apr 2025 none MIT — Details →
20.0.0-next.5 04 Apr 2025 none MIT — Details →
20.0.0-next.4 03 Apr 2025 none MIT — Details →
20.0.0-next.3 02 Apr 2025 none MIT — Details →
19.2.1 02 Apr 2025 none MIT — Details →
20.0.0-next.2 27 Mar 2025 none MIT — Details →
20.0.0-next.1 04 Mar 2025 none MIT — Details →
20.0.0-next.0 03 Mar 2025 none MIT — Details →
19.2.0 25 Feb 2025 none MIT — Details →
19.2.0-next.2 10 Feb 2025 none MIT — Details →
19.2.0-next.1 29 Jan 2025 none MIT — Details →
19.1.2 29 Jan 2025 none MIT — Details →
19.2.0-next.0 24 Jan 2025 none MIT — Details →
19.1.1 24 Jan 2025 none MIT — Details →
19.1.0 15 Jan 2025 none MIT — Details →
19.1.0-next.4 15 Jan 2025 none MIT — Details →
19.1.0-next.3 07 Jan 2025 none MIT — Details →
19.1.0-next.2 29 Nov 2024 none MIT — Details →
19.1.0-next.1 29 Nov 2024 none MIT — Details →
19.1.0-next.0 28 Nov 2024 none MIT — Details →
19.0.1 22 Nov 2024 none MIT — Details →
19.0.0 19 Nov 2024 none MIT — Details →
19.0.0-rc.0 31 Oct 2024 none MIT — Details →
19.0.0-next.7 24 Oct 2024 none MIT — Details →
19.0.0-next.6 15 Oct 2024 none MIT — Details →
19.0.0-next.5 15 Oct 2024 none MIT — Details →
19.0.0-next.3 28 Aug 2024 none MIT — Details →
19.0.0-next.2 28 Aug 2024 none MIT — Details →
19.0.0-next.1 21 Aug 2024 none MIT — Details →
18.2.1 21 Aug 2024 none — — Details →
19.0.0-next.0 14 Aug 2024 none — — Details →
18.2.0 14 Aug 2024 none — — Details →
18.2.0-next.0 10 Jul 2024 none — — Details →
18.1.0 10 Jul 2024 none — — Details →
18.1.0-next.0 25 Jun 2024 none — — Details →
18.0.0 22 May 2024 none — — Details →
18.0.0-rc.0 02 May 2024 none — — Details →
18.0.0-next.4 25 Apr 2024 none — — Details →
18.0.0-next.3 18 Apr 2024 none — — Details →
18.0.0-next.2 18 Apr 2024 none — — Details →
18.0.0-next.1 19 Mar 2024 none — — Details →
18.0.0-next.0 15 Mar 2024 none — — Details →
17.3.0 13 Mar 2024 none — — Details →
17.3.0-rc.0 06 Mar 2024 none — — Details →
17.2.1 04 Mar 2024 none — — Details →
17.2.0 14 Feb 2024 none — — Details →
17.2.0-rc.0 07 Feb 2024 none — — Details →
17.2.0-next.0 01 Feb 2024 none — — Details →
17.1.2 24 Jan 2024 none — — Details →

The newest 120 of 415 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 1

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

03 Vulnerabilities

Recorded vulnerabilities for ng-packagr

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-7735: OS Command Injection in ng-packagr 6.6 medium 10.1.1 07 May 2021

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 ng-packagr

Is ng-packagr safe to use?

Vulert records 1 vulnerabilities for ng-packagr in npm: 0 critical, 0 high, 1 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is ng-packagr's Vulert package health score?

Vulert scores ng-packagr 80/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 ng-packagr affected?

No. 22.2.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.

Which version of ng-packagr should I use?

22.2.4 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 ng-packagr have?

1 vulnerability is recorded for ng-packagr in the npm ecosystem: 0 critical, 0 high, 1 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 ng-packagr vulnerabilities disclosed?

0 vulnerabilities were recorded for ng-packagr in the last 12 months, and the oldest entry in this database dates to 07 May 2021. 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 ng-packagr 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 ng-packagr for upcoming vulnerabilities?

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