@angular/build
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 | net-exec-file:src/utils/index-file/auto-csp.js | AI (source-diff): auto-csp.js is a legitimate Angular build tool file implementing CSP header generation. The 'network+exec' pattern is a false positive — it's standard TypeScript compiled output for HTML processing, not malware. | ai | |
| dependencies | unvetted-dep:@angular-devkit/architect | AI (dependencies): @angular-devkit/architect is a first-party Angular DevKit package from the same Google/Angular org; not a real risk for this package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): rolldown replaces rollup (documented Angular CLI v21 migration); undici is a well-known Node.js HTTP client. Both are legitimate for this package. | ai | |
| phantom-deps | phantom-dep:source-map-support | AI (phantom-deps): source-map-support is a listed runtime dependency in package.json; phantom-dep finding is a false positive. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): google-wombot publishes Angular major versions on long cycles; v21 is a planned major release, not indicative of account takeover. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): process.env spread into worker options is standard for build tool worker processes; not exfiltration. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require in a build tool for optional Bazel plugin loading; legitimate and already marked accepted risk. | ai | |
| typosquat | typosquat.levenshtein:esbuild | AI (typosquat): @angular/build is the official Angular build system from Google's Angular org; not a typosquat of esbuild. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): @angular/build is the official Angular build system from Google's Angular org; not a typosquat of uuid. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding is used for JIT template data in Angular's compiler pipeline; not a malicious payload. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): new Function used as a well-known ESM dynamic import workaround in CJS contexts; standard pattern in Angular CLI. | ai |
Versions (showing 51 of 151)
| Version | Deps | Published |
|---|---|---|
| 21.2.13 | 27 / 0 | |
| 21.2.12 | 27 / 0 | |
| 21.2.11 | 27 / 0 | |
| 21.2.10 | 27 / 0 | |
| 21.2.9 | 27 / 0 | |
| 21.2.8 | 27 / 0 | |
| 21.2.7 | 27 / 0 | |
| 21.2.6 | 27 / 0 | |
| 21.2.5 | 27 / 0 | |
| 21.2.4 | 27 / 0 | |
| 21.2.3 | 27 / 0 | |
| 21.2.2 | 27 / 0 | |
| 21.2.1 | 27 / 0 | |
| 21.2.0 | 27 / 0 | |
| 21.1.5 | 27 / 0 | |
| 21.1.4 | 27 / 0 | |
| 21.1.3 | 27 / 0 | |
| 21.1.2 | 27 / 0 | |
| 21.1.1 | 27 / 0 | |
| 21.1.0 | 27 / 0 | |
| 21.0.6 | 27 / 0 | |
| 21.0.5 | 27 / 0 | |
| 21.0.4 | 27 / 0 | |
| 21.0.3 | 27 / 0 | |
| 21.0.2 | 27 / 0 | |
| 21.0.1 | 27 / 0 | |
| 21.0.0 | 27 / 0 | |
| 20.3.26 | 26 / 0 | |
| 20.3.25 | 26 / 0 | |
| 20.3.24 | 26 / 0 | |
| 20.3.23 | 26 / 0 | |
| 20.3.22 | 26 / 0 | |
| 20.3.21 | 26 / 0 | |
| 20.3.20 | 26 / 0 | |
| 20.3.19 | 26 / 0 | |
| 20.3.18 | 26 / 0 | |
| 20.3.17 | 26 / 0 | |
| 20.3.16 | 26 / 0 | |
| 20.3.15 | 26 / 0 | |
| 20.3.14 | 26 / 0 | |
| 20.3.13 | 26 / 0 | |
| 20.3.12 | 26 / 0 | |
| 20.3.11 | 26 / 0 | |
| 20.3.10 | 26 / 0 | |
| 20.3.9 | 26 / 0 | |
| 20.3.8 | 26 / 0 | |
| 20.3.7 | 26 / 0 | |
| 20.3.6 | 26 / 0 | |
| 20.3.5 | 26 / 0 | |
| 20.3.4 | 26 / 0 | |
| 20.3.3 | 26 / 0 |
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. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v21.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.0
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. Consider requesting the maintainer enable provenance via CI/CD.
v20.3.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.3.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.3.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.3.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.3.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.3.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.3.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.3.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.3.4
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.3.3
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.