@schematics/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 — 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 |
|---|---|---|---|---|
| semgrep | semgrep:env-spread | AI (semgrep): Standard pattern in Angular CLI build tooling for passing env vars to child processes; already annotated as accepted risk in the codebase. Stable false positive for this package. | ai |
Versions (showing 51 of 165)
| Version | Deps | Published |
|---|---|---|
| 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.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 | |
| 20.3.8 | 3 / 0 | |
| 20.3.7 | 3 / 0 | |
| 20.3.6 | 3 / 0 | |
| 20.3.5 | 3 / 0 | |
| 20.3.4 | 3 / 0 | |
| 20.3.3 | 3 / 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
2 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/angular/angular-cli/blob/877230c589598f735ff555ba1807e9dce078d3d3/workspace/index.js#L24 22 | encoding: 'utf8', 23 | stdio: 'pipe', > 24 | env: { 25 | ...process.env, 26 | // NPM updater notifier will prevents the child process from closing until it timeout after 3 m
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Consider requesting the maintainer enable provenance via CI/CD.
v21.2.4
2 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/angular/angular-cli/blob/1ea622bdd2d4583d3a71851752a4a9b5ca321164/workspace/index.js#L24 22 | encoding: 'utf8', 23 | stdio: 'pipe', > 24 | env: { 25 | ...process.env, 26 | // NPM updater notifier will prevents the child process from closing until it timeout after 3 m
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. 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
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.