simple-log-methods
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 |
|---|---|---|---|---|
| install-scripts | install-script:postinstall | AI (install-scripts): Husky git-hooks guard; only executes in dev environments with a .git dir, harmless to downstream consumers. | ai | |
| phantom-deps | phantom-dep:domain-objects | AI (phantom-deps): Referenced in config files only, not directly imported at runtime; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@ehmpathy/error-fns | AI (phantom-deps): Referenced in config files only, not directly imported at runtime; stable false positive for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.6.12 | 6 / 29 | |
| 0.6.11 | 6 / 29 | |
| 0.6.10 | 6 / 29 | |
| 0.6.9 | 6 / 27 | |
| 0.6.8 | 6 / 27 | |
| 0.6.7 | 6 / 27 | |
| 0.6.5 | 6 / 23 | |
| 0.6.4 | 6 / 23 | |
| 0.6.3 | 4 / 26 | |
| 0.6.2 | 4 / 24 |
v0.6.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.3
2 findingsScript: [ -d .git ] && npm run prepare:husky || exit 0
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.2
2 findingsScript: [ -d .git ] && npm run prepare:husky || exit 0
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.