@angular/build No license 51 versions

@angular/build

npm Repository Homepage

51

Versions

—

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

angulargoogle-wombot

Keywords

Angular CLIAngular DevKitangularangular-clidevkitsdk

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	2026/04/24
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	2026/04/23
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	2026/04/23
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	2026/04/23
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	2026/04/23
semgrep	semgrep:env-spread	AI (semgrep): process.env spread into worker options is standard for build tool worker processes; not exfiltration.	ai	2026/04/23
semgrep	semgrep:dynamic-require	AI (semgrep): Dynamic require in a build tool for optional Bazel plugin loading; legitimate and already marked accepted risk.	ai	2026/04/23
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	2026/04/23
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	2026/04/23
semgrep	semgrep:base64-decode	AI (semgrep): Base64 decoding is used for JIT template data in Angular's compiler pipeline; not a malicious payload.	ai	2026/04/23
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	2026/04/23

Versions (showing 51 of 151)

Version	Deps	Published
19.1.7	26 / 0	2025-02-12
19.1.6	26 / 0	2025-02-05
19.1.5	26 / 0	2025-01-29
19.1.4	25 / 0	2025-01-22
19.1.3	25 / 0	2025-01-20
19.1.2	25 / 0	2025-01-17
19.1.1	25 / 0	2025-01-16
19.1.0	25 / 0	2025-01-15
19.0.7	25 / 0	2025-01-08
19.0.6	25 / 0	2024-12-18
19.0.5	25 / 0	2024-12-12
19.0.4	25 / 0	2024-12-05
19.0.3	25 / 0	2024-12-04
19.0.2	25 / 0	2024-11-25
19.0.1	25 / 0	2024-11-21
19.0.0	25 / 0	2024-11-19
18.2.21	25 / 0	2025-09-10
18.2.20	25 / 0	2025-06-11
18.2.19	25 / 0	2025-04-23
18.2.18	25 / 0	2025-04-09
18.2.17	25 / 0	2025-04-02
18.2.16	25 / 0	2025-03-26
18.2.15	25 / 0	2025-03-13
18.2.14	25 / 0	2025-01-29
18.2.13	25 / 0	2025-01-29
18.2.12	25 / 0	2024-11-14
18.2.11	25 / 0	2024-10-30
18.2.10	25 / 0	2024-10-23
18.2.9	25 / 0	2024-10-16
18.2.8	25 / 0	2024-10-09
18.2.7	25 / 0	2024-10-02
18.2.6	25 / 0	2024-09-25
18.2.5	25 / 0	2024-09-18
18.2.4	25 / 0	2024-09-11
18.2.3	25 / 0	2024-09-04
18.2.2	25 / 0	2024-08-29
18.2.1	25 / 0	2024-08-21
18.2.0	25 / 0	2024-08-14
18.1.4	27 / 0	2024-08-07
18.1.3	27 / 0	2024-07-31
18.1.2	27 / 0	2024-07-24
18.1.1	27 / 0	2024-07-17
18.1.0	27 / 0	2024-07-10
18.0.7	25 / 0	2024-07-03
18.0.6	25 / 0	2024-06-26
18.0.5	25 / 0	2024-06-20
18.0.4	25 / 0	2024-06-13
18.0.3	25 / 0	2024-06-05
18.0.2	25 / 0	2024-05-29
18.0.1	25 / 0	2024-05-23
18.0.0	25 / 0	2024-05-22

v19.1.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v19.1.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v19.1.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v19.1.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v19.1.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v19.1.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v19.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v19.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v19.0.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v19.0.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v19.0.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v19.0.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v19.0.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v19.0.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v19.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v19.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v18.2.21

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v18.2.20

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v18.2.19

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v18.2.18

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v18.2.17

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v18.2.16

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v18.2.15

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v18.2.14

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v18.2.13

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v18.2.12

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v18.2.11

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v18.2.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v18.2.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v18.2.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v18.2.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v18.2.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v18.2.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v18.2.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v18.2.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v18.2.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v18.2.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v18.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v18.1.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v18.1.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v18.1.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v18.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v18.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v18.0.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v18.0.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v18.0.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v18.0.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v18.0.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v18.0.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v18.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v18.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.