@angular/platform-server
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | rapid-publish | AI (publish-pattern): Angular publishes many scoped packages in rapid succession; expected pattern. | ai | |
| source-diff | obfuscated-file:fesm2022/server-D0hkX0bF.mjs | AI (source-diff): Standard Angular FESM2022 bundle with source map; stable pattern across versions. | ai | |
| source-diff | obfuscated-file:fesm2022/server-Bnqydiu0.mjs | AI (source-diff): Standard Angular FESM bundle with bundled domino; long lines are normal build output. | ai | |
| source-diff | obfuscated-file:fesm2022/server-AMcurffX.mjs | AI (source-diff): Standard Angular FESM bundle with inlined domino; long lines from bundling, not obfuscation. | ai | |
| source-diff | obfuscated-file:fesm2022/server.mjs | AI (source-diff): Standard Angular FESM2022 bundle with long import lines; not obfuscation. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Official Angular scoped package; no-keywords/short-readme is normal for framework sub-packages. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit runtime dep for TypeScript-compiled packages. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 22.0.0 | 2 / 0 | |
| 21.2.16 | 2 / 0 | |
| 21.2.15 | 2 / 0 | |
| 21.2.14 | 2 / 0 | |
| 21.2.13 | 2 / 0 | |
| 21.2.12 | 2 / 0 | |
| 21.2.11 | 2 / 0 | |
| 21.2.10 | 2 / 0 | |
| 21.2.9 | 2 / 0 | |
| 20.3.24 | 2 / 0 | |
| 20.3.23 | 2 / 0 | |
| 20.3.22 | 2 / 0 | |
| 20.3.21 | 2 / 0 | |
| 20.3.20 | 2 / 0 | |
| 20.3.19 | 2 / 0 | |
| 19.2.25 | 2 / 0 | |
| 19.2.24 | 2 / 0 | |
| 19.2.23 | 2 / 0 | |
| 19.2.22 | 2 / 0 | |
| 19.2.21 | 2 / 0 |
v22.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.2.14
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: google-wombot.
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. Consider requesting the maintainer enable provenance via CI/CD.
v21.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.
v20.3.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.3.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.3.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.3.21
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.3.20
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.3.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.2.25
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.2.24
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.2.23
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.2.22
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.2.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.