secure-random-octet
Generate a cryptographically secure octet
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): SLSA provenance attestation present; gitHead absence is a cosmetic metadata gap, not a supply chain risk. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase explained by dual CJS/ESM build output with TypeScript declarations; no injected payload. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 6.0.0 | 1 / 9 | |
| 5.0.4 | 1 / 10 | |
| 5.0.3 | 1 / 10 | |
| 5.0.2 | 1 / 11 | |
| 5.0.1 | 1 / 11 | |
| 5.0.0 | 1 / 11 |
v6.0.0
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: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.