@angular/platform-browser-dynamic
Angular - library for using Angular in a web browser with JIT compilation
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): google-wombot is the official Angular publish bot; missing gitHead reflects a CI pipeline change, not a security concern, for this well-established Google-maintained package. | ai | |
| provenance | no-provenance | AI (provenance): Official Angular package published by google-wombot with a long established track record; lack of Sigstore attestation is a hygiene gap, not a security risk for this package. | ai | |
| source-diff | obfuscated-file:esm2022/testing/src/dom_test_component_renderer.mjs | AI (source-diff): Angular ESM2022 compiled output with Google copyright headers; long lines are generated metadata/decorators, not obfuscation. Stable false positive for Angular packages. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase reflects Angular's addition of granular ESM2022 source files per the updated export map. Expected structural change in Angular's packaging, not payload injection. | ai | |
| source-diff | obfuscated-file:esm2022/src/resource_loader/resource_loader_impl.mjs | AI (source-diff): Angular ESM2022 compiled output with Google copyright headers; long lines are generated metadata/decorators, not obfuscation. Stable false positive for Angular packages. | ai | |
| source-diff | obfuscated-file:esm2022/src/compiler_factory.mjs | AI (source-diff): Angular ESM2022 compiled output with Google copyright headers; long lines are generated metadata/decorators, not obfuscation. Stable false positive for Angular packages. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a well-known implicit runtime dependency for Angular packages; this is a stable false positive across all versions of this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Angular framework packages don't need keywords or elaborate READMEs on npm; these cosmetic signals are stable false positives for this package. | ai |
Versions (showing 100 of 577)
| Version | Deps | Published |
|---|---|---|
| 19.2.2 | 1 / 0 | |
| 19.2.1 | 1 / 0 | |
| 19.2.0 | 1 / 0 | |
| 19.1.8 | 1 / 0 | |
| 19.1.7 | 1 / 0 | |
| 19.1.6 | 1 / 0 | |
| 19.1.5 | 1 / 0 | |
| 19.1.4 | 1 / 0 | |
| 19.1.3 | 1 / 0 | |
| 19.1.2 | 1 / 0 | |
| 19.1.1 | 1 / 0 | |
| 19.1.0 | 1 / 0 | |
| 19.0.7 | 1 / 0 | |
| 19.0.6 | 1 / 0 | |
| 19.0.5 | 1 / 0 | |
| 19.0.4 | 1 / 0 | |
| 19.0.3 | 1 / 0 | |
| 19.0.2 | 1 / 0 | |
| 19.0.1 | 1 / 0 | |
| 19.0.0 | 1 / 0 | |
| 18.2.14 | 1 / 0 | |
| 18.2.13 | 1 / 0 | |
| 18.2.12 | 1 / 0 | |
| 18.2.11 | 1 / 0 | |
| 18.2.10 | 1 / 0 | |
| 18.2.9 | 1 / 0 | |
| 18.2.8 | 1 / 0 | |
| 18.2.7 | 1 / 0 | |
| 18.2.6 | 1 / 0 | |
| 18.2.5 | 1 / 0 | |
| 18.2.4 | 1 / 0 | |
| 18.2.3 | 1 / 0 | |
| 18.2.2 | 1 / 0 | |
| 18.2.1 | 1 / 0 | |
| 18.2.0 | 1 / 0 | |
| 18.1.5 | 1 / 0 | |
| 18.1.4 | 1 / 0 | |
| 18.1.3 | 1 / 0 | |
| 18.1.2 | 1 / 0 | |
| 18.1.1 | 1 / 0 | |
| 18.1.0 | 1 / 0 | |
| 18.0.7 | 1 / 0 | |
| 18.0.6 | 1 / 0 | |
| 18.0.5 | 1 / 0 | |
| 18.0.4 | 1 / 0 | |
| 18.0.3 | 1 / 0 | |
| 18.0.2 | 1 / 0 | |
| 18.0.1 | 1 / 0 | |
| 18.0.0 | 1 / 0 | |
| 17.3.12 | 1 / 0 | |
| 17.3.11 | 1 / 0 | |
| 17.3.10 | 1 / 0 | |
| 17.3.9 | 1 / 0 | |
| 17.3.8 | 1 / 0 | |
| 17.3.7 | 1 / 0 | |
| 17.3.6 | 1 / 0 | |
| 17.3.5 | 1 / 0 | |
| 17.3.4 | 1 / 0 | |
| 17.3.3 | 1 / 0 | |
| 17.3.2 | 1 / 0 | |
| 17.3.1 | 1 / 0 | |
| 17.3.0 | 1 / 0 | |
| 17.2.4 | 1 / 0 | |
| 17.2.3 | 1 / 0 | |
| 17.2.2 | 1 / 0 | |
| 17.2.1 | 1 / 0 | |
| 17.2.0 | 1 / 0 | |
| 17.1.3 | 1 / 0 | |
| 17.1.2 | 1 / 0 | |
| 17.1.1 | 1 / 0 | |
| 17.1.0 | 1 / 0 | |
| 17.0.9 | 1 / 0 | |
| 17.0.8 | 1 / 0 | |
| 17.0.7 | 1 / 0 | |
| 17.0.6 | 1 / 0 | |
| 17.0.5 | 1 / 0 | |
| 17.0.4 | 1 / 0 | |
| 17.0.3 | 1 / 0 | |
| 17.0.2 | 1 / 0 | |
| 17.0.1 | 1 / 0 | |
| 17.0.0 | 1 / 0 | |
| 16.2.12 | 1 / 0 | |
| 16.2.11 | 1 / 0 | |
| 16.2.10 | 1 / 0 | |
| 16.2.9 | 1 / 0 | |
| 16.2.8 | 1 / 0 | |
| 16.2.7 | 1 / 0 | |
| 16.2.6 | 1 / 0 | |
| 16.2.5 | 1 / 0 | |
| 16.2.4 | 1 / 0 | |
| 16.2.3 | 1 / 0 | |
| 16.2.2 | 1 / 0 | |
| 16.2.1 | 1 / 0 | |
| 16.2.0 | 1 / 0 | |
| 16.1.9 | 1 / 0 | |
| 16.1.8 | 1 / 0 | |
| 16.1.7 | 1 / 0 | |
| 16.1.6 | 1 / 0 | |
| 16.1.5 | 1 / 0 | |
| 16.1.4 | 1 / 0 |
v17.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.