unique-filename
Generate a unique filename for use in temporary directories or caches.
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Package is published by the npm CLI team; transition to GitHub Actions CI/CD publisher is the standard npm org workflow and is verified by SLSA provenance attestation. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): owlstronaut is an npm CLI team member; maintainer roster changes are expected for this npm org package. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): fritzy removal is consistent with npm CLI team maintainer transitions; package remains under npm org control with SLSA attestation. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by a SLSA-attested GitHub Actions publish from the npm org is a legitimate release pattern, not a takeover indicator. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 6.0.0 | 1 / 2 | |
| 5.0.0 | 1 / 3 | |
| 4.0.0 | 1 / 3 | |
| 3.0.0 | 1 / 3 | |
| 2.0.1 | 1 / 3 | |
| 2.0.0 | 1 / 3 | |
| 1.1.1 | 1 / 2 | |
| 1.1.0 | 1 / 2 | |
| 1.0.0 | 1 / 2 |
v6.0.0
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
2 findingsThis version was published by a different npm account than previous versions on 2025-10-22. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2024-09-26. This could indicate a legitimate maintainer transition or an account compromise.