StackPrism

npm package

@angular/core 20.3.31: no known vulnerabilities

@angular/core 20.3.31 has no known vulnerabilities in OSV.dev. Angular 20 reaches end of life on Nov 28, 2026. Move to Angular 22.

npm (opens in a new tab) describes it as “Angular - the core framework”

Known vulnerabilities
0
None in OSV.dev
Released
Sep 9, 2026
Latest is 22.2.3
Downloads last week
52.3K
Under 1% of @angular/core downloads
Angular 20 support
Ending soon
Until Nov 28, 2026
Licence
MIT
OpenSSF Scorecard
8.3/10
angular/angular (opens in a new tab)
Pulls in
1 package
Resolved by deps.dev

Newer releases

20.3.31 has nothing to fix today. Newer releases, for when you upgrade:

  • 20.3.34

    Newest 20.x release. Released Oct 14, 2026.

    No known vulnerabilities

  • 22.2.3

    Latest release. Released Oct 14, 2026.

    No known vulnerabilities

Hand the fix to your coding agent

One task with the upgrade, the file to change and why. Paste it into Claude Code, Cursor or Codex.

Findings

Who is still on a vulnerable @angular/core

54% of last week’s 6.2M @angular/core downloads went to versions with known vulnerabilities.

From npm’s per-version download counts for the last 7 days, each version checked against OSV.dev. The versions checked cover 98% of downloads.

Is @angular/core the only one?

Paste a public GitHub repo or drop your package.json and see every vulnerable, end-of-life or deprecated dependency, with one fix task. Free, no sign-up.

Check your whole repo

How this page is checked

StackPrism asks OSV.dev which advisories affect exactly @angular/core 20.3.31, merges duplicates filed under several ids, and ranks them with CISA’s Known Exploited Vulnerabilities list and FIRST EPSS. Release dates and deprecation come from deps.dev and npm, support dates from endoflife.date. No AI writes this page: every sentence comes from that data, refreshed every few hours.

Last checked against npm, OSV.dev, deps.dev and endoflife.date.