@pawel-up/benchmark
8
Versions
—
License
No
Install Scripts
Verified
Provenance
Supply chain provenance
Status for the latest visible version.
SLSA provenance attestation
npm registry signatures
gitHead linked
Maintainers
jarrodek
Keywords
benchmarktesting
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI/CD publisher with SLSA attestation; consistent with automation of releases. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by feature release with SLSA provenance; no malicious indicators present. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.1.1 | 3 / 27 | |
| 1.1.0 | 3 / 27 | |
| 1.0.5 | 3 / 20 | |
| 1.0.4 | 3 / 20 | |
| 1.0.3 | 3 / 20 | |
| 1.0.2 | 3 / 20 | |
| 1.0.1 | 3 / 20 | |
| 1.0.0 | 3 / 20 |
v1.0.1
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.