@angular/pwa
PWA schematics for Angular
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:new-function-constructor | AI (semgrep): Dynamic ESM import shim in Angular CLI source, not arbitrary code exec. | ai | |
| phantom-deps | phantom-dep:parse5-html-rewriting-stream | AI (phantom-deps): Used indirectly via schematics config; declared dep is intentional. | ai | |
| typosquat | typosquat.levenshtein:koa | AI (typosquat): Official Angular package; unrelated to koa, false positive. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Official Angular package; unrelated to pg, false positive. | ai |
Versions (showing 74 of 74)
| Version | Deps | Published |
|---|---|---|
| 22.0.8 | 3 / 0 | |
| 22.0.7 | 3 / 0 | |
| 22.0.6 | 3 / 0 | |
| 22.0.5 | 3 / 0 | |
| 22.0.4 | 3 / 0 | |
| 22.0.3 | 3 / 0 | |
| 22.0.2 | 3 / 0 | |
| 22.0.1 | 3 / 0 | |
| 22.0.0 | 3 / 0 | |
| 21.2.19 | 3 / 0 | |
| 21.2.18 | 3 / 0 | |
| 21.2.17 | 3 / 0 | |
| 21.2.16 | 3 / 0 | |
| 21.2.15 | 3 / 0 | |
| 21.2.14 | 3 / 0 | |
| 21.2.13 | 3 / 0 | |
| 21.2.12 | 3 / 0 | |
| 21.2.11 | 3 / 0 | |
| 21.2.10 | 3 / 0 | |
| 21.2.9 | 3 / 0 | |
| 21.2.8 | 3 / 0 | |
| 21.2.7 | 3 / 0 | |
| 21.2.6 | 3 / 0 | |
| 21.2.5 | 3 / 0 | |
| 21.2.4 | 3 / 0 | |
| 21.2.3 | 3 / 0 | |
| 21.2.2 | 3 / 0 | |
| 21.2.1 | 3 / 0 | |
| 21.2.0 | 3 / 0 | |
| 21.1.5 | 3 / 0 | |
| 21.1.4 | 3 / 0 | |
| 21.1.3 | 3 / 0 | |
| 21.1.2 | 3 / 0 | |
| 21.1.1 | 3 / 0 | |
| 21.1.0 | 3 / 0 | |
| 21.0.6 | 3 / 0 | |
| 21.0.5 | 3 / 0 | |
| 21.0.4 | 3 / 0 | |
| 21.0.3 | 3 / 0 | |
| 21.0.2 | 3 / 0 | |
| 21.0.1 | 3 / 0 | |
| 21.0.0 | 3 / 0 | |
| 20.3.32 | 3 / 0 | |
| 20.3.31 | 3 / 0 | |
| 20.3.30 | 3 / 0 | |
| 20.3.29 | 3 / 0 | |
| 20.3.28 | 3 / 0 | |
| 20.3.27 | 3 / 0 | |
| 20.3.26 | 3 / 0 | |
| 20.3.25 | 3 / 0 | |
| 20.3.24 | 3 / 0 | |
| 20.3.23 | 3 / 0 | |
| 20.3.22 | 3 / 0 | |
| 20.3.21 | 3 / 0 | |
| 20.3.20 | 3 / 0 | |
| 20.3.19 | 3 / 0 | |
| 20.3.18 | 3 / 0 | |
| 20.3.17 | 3 / 0 | |
| 20.3.16 | 3 / 0 | |
| 20.3.15 | 3 / 0 | |
| 20.3.14 | 3 / 0 | |
| 20.3.13 | 3 / 0 | |
| 20.3.12 | 3 / 0 | |
| 20.3.11 | 3 / 0 | |
| 20.3.10 | 3 / 0 | |
| 20.3.9 | 3 / 0 | |
| 19.2.27 | 3 / 0 | |
| 19.2.26 | 3 / 0 | |
| 19.2.25 | 3 / 0 | |
| 19.2.24 | 3 / 0 | |
| 19.2.23 | 3 / 0 | |
| 19.2.22 | 3 / 0 | |
| 19.2.21 | 3 / 0 | |
| 19.2.20 | 3 / 0 |
v22.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.2.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.2.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.3.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.3.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.
v19.2.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.2.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.2.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.