pandemonium
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:mnemonist | AI (dependencies): mnemonist is authored by the same publisher (yomguithereal) and is a well-known, legitimate data structures library. This finding is a stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Lack of provenance is common (~88% of packages) and not a risk signal for this well-established, trusted package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 2.4.1 | 1 / 8 | |
| 2.4.0 | 1 / 8 | |
| 2.3.0 | 1 / 8 | |
| 2.2.0 | 0 / 9 | |
| 2.1.0 | 0 / 8 | |
| 2.0.0 | 0 / 5 |
v2.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.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.