@angular/compiler
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:types/compiler.d.ts | AI (source-diff): types/compiler.d.ts is a standard TypeScript declaration file for the Angular compiler. Long lines are due to complex type declarations, not obfuscation. This is expected for large Angular packages. | ai | |
| source-diff | obfuscated-file:index.d.ts | AI (source-diff): Angular packages ship large bundled .d.ts declaration files that trigger long-line heuristics. The sample confirms human-readable TypeScript declarations, not obfuscated code. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a standard TypeScript runtime helper used implicitly by Angular's compiled output; this is expected and benign for all Angular packages. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 21.2.15 | 1 / 0 | |
| 21.2.14 | 1 / 0 | |
| 21.2.13 | 1 / 0 | |
| 21.2.12 | 1 / 0 | |
| 21.2.11 | 1 / 0 | |
| 21.2.10 | 1 / 0 | |
| 21.2.9 | 1 / 0 | |
| 21.2.8 | 1 / 0 | |
| 21.2.7 | 1 / 0 | |
| 21.2.6 | 1 / 0 | |
| 21.2.5 | 1 / 0 | |
| 21.2.4 | 1 / 0 | |
| 20.3.23 | 1 / 0 | |
| 20.3.22 | 1 / 0 | |
| 20.3.21 | 1 / 0 | |
| 20.3.20 | 1 / 0 | |
| 20.3.19 | 1 / 0 | |
| 20.3.18 | 1 / 0 | |
| 19.2.24 | 1 / 0 | |
| 19.2.23 | 1 / 0 | |
| 19.2.22 | 1 / 0 | |
| 19.2.21 | 1 / 0 | |
| 19.2.20 | 1 / 0 |
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. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v21.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.2.5
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.
v21.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.3.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.3.19
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.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.2.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.2.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.2.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.2.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.
v19.2.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.