jest-preset-angular
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Moved from named contributor (anhpnnd) to GitHub Actions CI with SLSA provenance; legitimate CI migration. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Major version bump cycle for Angular ecosystem; dormancy reflects normal release cadence. | ai | |
| phantom-deps | phantom-dep:esbuild-wasm | AI (phantom-deps): esbuild-wasm is a fallback for esbuild (optional dep); declared intentionally. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 16.2.0 | 6 / 59 | |
| 16.1.5 | 6 / 59 | |
| 16.1.4 | 6 / 59 | |
| 16.1.3 | 6 / 59 | |
| 16.1.2 | 6 / 59 | |
| 16.1.1 | 6 / 59 | |
| 16.1.0 | 6 / 59 | |
| 16.0.0 | 6 / 59 |
v16.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v16.1.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v16.1.4
2 findingsThis version was published by a different npm account than previous versions on 2026-04-09. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v16.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.