snooplogg
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/index.mjs | AI (source-diff): Minified ESM bundle produced by tsdown build tool; expected artifact for this package. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 9.0.0 | 0 / 11 | |
| 8.0.0 | 0 / 11 | |
| 7.0.2 | 0 / 11 | |
| 7.0.1 | 0 / 11 | |
| 7.0.0 | 0 / 11 | |
| 6.1.1 | 0 / 13 | |
| 6.1.0 | 0 / 13 | |
| 6.0.3 | 0 / 13 | |
| 6.0.2 | 0 / 16 | |
| 6.0.1 | 0 / 16 | |
| 6.0.0 | 0 / 16 |
v9.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.