bootstrap.native
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@thednp/shorty | AI (dependencies): First-party dependency from same publisher (thednp); stable utility for this package. | ai | |
| dependencies | unvetted-dep:@thednp/event-listener | AI (dependencies): First-party dependency from same publisher (thednp); stable utility for this package. | ai | |
| dependencies | unvetted-dep:@thednp/position-observer | AI (dependencies): First-party dependency from same publisher (thednp); stable utility for this package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 5.1.10 | 3 / 11 | |
| 5.1.9 | 3 / 11 | |
| 5.1.8 | 3 / 12 | |
| 5.1.7 | 3 / 12 | |
| 5.1.6 | 3 / 10 | |
| 5.1.5 | 3 / 10 | |
| 5.1.4 | 3 / 10 | |
| 5.1.3 | 3 / 10 |
v5.1.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.