fast-shuffle
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:fn-pcg | AI (dependencies): Small, purpose-fit RNG dependency from same domain; not a security concern. | ai | |
| provenance | no-provenance | AI (provenance): Established package with 28 versions and 2989 days of history; lack of provenance is common and not a security concern here. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 6.2.0 | 1 / 11 | |
| 6.1.1 | 1 / 15 | |
| 6.1.0 | 1 / 17 | |
| 6.0.1 | 1 / 17 | |
| 6.0.0 | 1 / 17 |
v6.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.