@angular/ssr
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | encoded-string-file:third_party/beasties/index.js | AI (source-diff): HTML entity decode map from beasties library; stable bundled third-party asset in Angular SSR. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped @angular/ssr package; Levenshtein match against 'qs' is a heuristic false positive with no real typosquat risk. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): base64 decode is in vendored beasties CSS inliner (third_party/); benign utility use, not a payload. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit Angular/TypeScript runtime dependency; stable false positive for Angular packages. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 22.0.0 | 1 / 9 | |
| 21.2.14 | 1 / 9 | |
| 21.2.13 | 1 / 9 | |
| 21.2.12 | 1 / 9 | |
| 21.2.11 | 1 / 9 | |
| 21.2.10 | 1 / 9 | |
| 21.2.9 | 1 / 9 | |
| 21.2.7 | 1 / 9 | |
| 20.3.27 | 1 / 8 | |
| 20.3.26 | 1 / 8 | |
| 20.3.25 | 1 / 8 | |
| 19.2.27 | 1 / 8 | |
| 19.2.26 | 1 / 8 | |
| 19.2.25 | 1 / 8 |
v22.0.0
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.2.14
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.2.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.3.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.3.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.3.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.2.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.2.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.2.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.