beasties
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 | missing-githead | AI (provenance): danielroe is a long-standing trusted publisher; missing gitHead reflects a publish environment change, not a security concern for this package. | ai | |
| provenance | no-provenance | AI (provenance): Lack of Sigstore provenance is a process gap, not a security threat, for this established package from a trusted publisher. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): 0.0.0 is a placeholder/stub release pattern used by this trusted publisher (danielroe); not indicative of malicious intent for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Stub release by a well-established publisher with 1875 days of history; minimal metadata is consistent with a namespace reservation or initial scaffold, not spam/malware. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.4.2 | 9 / 3 | |
| 0.4.1 | 9 / 3 | |
| 0.4.0 | 9 / 3 | |
| 0.3.5 | 8 / 3 | |
| 0.3.4 | 8 / 3 | |
| 0.3.3 | 8 / 3 | |
| 0.3.2 | 8 / 3 | |
| 0.3.1 | 8 / 3 | |
| 0.3.0 | 8 / 3 | |
| 0.2.0 | 8 / 3 | |
| 0.1.0 | 8 / 3 | |
| 0.0.26 | 7 / 2 | |
| 0.0.0 | 0 / 0 |
v0.4.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: danielroe.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: danielroe.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.