| Rule | Check | Points |
|---|---|---|
| Vulnerabilities | A critical or high vulnerability in the version recommended for the major | score 0 |
| Each moderate vulnerability in that version | −5 | |
| Each low vulnerability in that version | −2 | |
| Support | Each of the 3 most recent majors (the major and the ones before it) with no stable version | −10 |
| Stale releases | Each recent major served by the version that already served the major before it, published before that major came out | −5 |
| Maturity | The recommended version is still 0.x | −20 |
| Popularity | Fewer than 1,000 weekly downloads on npm | −10 |
| Maintenance | Deprecated on npm, or the repository archived on GitHub | −30 |
Grades
Good from 80, fair from 60, poor below. A critical or high vulnerability in the version you would install sets the score to 0 whatever the rest: the badge shows a warning sign instead of a number.
One score per major
The headline score is for Angular 22. Each library page also scores every major since 14, as if it were the one your project runs: the support and stale-release rules look at that major and the ones before it, and the vulnerabilities are those of the version recommended for it.
Where the facts come from
- Version per major: the newest stable release on npm whose peer dependency range on
@angular/core(or another@angular/*package when the library declares none on core) accepts the major. An open range such as>=16.0.0accepts every later major: that is how its author declared it, hence the stale-release rule. - Advisories: the GitHub Advisory Database, where npm's own advisories come from, for the library itself. Its dependencies are not audited.
- Downloads: npm's weekly count.
- Deprecated, archived: the deprecation flag of the latest version on npm; the archived flag of the GitHub repository the package declares.
The data is refreshed every week. The list of libraries is curated in the repository: a missing one is a pull request on libraries.json.