gunshi
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Package consistently published via GitHub Actions CI/CD with SLSA attestation; kazupon→GitHub Actions is an expected automation transition. | ai | |
| dependencies | unvetted-dep:args-tokens | AI (dependencies): args-tokens appears to be a companion package by the same author; low risk for this CLI library. | ai |
Versions (showing 77 of 77)
| Version | Deps | Published |
|---|---|---|
| 0.37.1 | 0 / 13 | |
| 0.37.0 | 0 / 13 | |
| 0.36.0 | 0 / 13 | |
| 0.35.3 | 0 / 13 | |
| 0.35.2 | 0 / 13 | |
| 0.35.1 | 0 / 13 | |
| 0.35.0 | 0 / 13 | |
| 0.34.0 | 0 / 13 | |
| 0.33.0 | 0 / 13 | |
| 0.32.0 | 0 / 13 | |
| 0.31.0 | 0 / 13 | |
| 0.30.8 | 0 / 12 | |
| 0.30.7 | 0 / 12 | |
| 0.30.6 | 0 / 12 | |
| 0.30.5 | 0 / 12 | |
| 0.30.3 | 0 / 12 | |
| 0.30.1 | 0 / 12 | |
| 0.30.0 | 0 / 12 | |
| 0.29.5 | 0 / 12 | |
| 0.29.4 | 0 / 12 | |
| 0.29.3 | 0 / 12 | |
| 0.29.2 | 0 / 12 | |
| 0.29.1 | 0 / 12 | |
| 0.28.2 | 0 / 12 | |
| 0.28.0 | 0 / 12 | |
| 0.27.6 | 0 / 12 | |
| 0.27.5 | 1 / 11 | |
| 0.27.4 | 1 / 11 | |
| 0.27.3 | 1 / 11 | |
| 0.27.0 | 1 / 11 | |
| 0.26.3 | 1 / 8 | |
| 0.26.2 | 1 / 8 | |
| 0.26.1 | 1 / 8 | |
| 0.26.0 | 1 / 8 | |
| 0.25.1 | 1 / 8 | |
| 0.25.0 | 1 / 44 | |
| 0.24.0 | 1 / 43 | |
| 0.23.1 | 1 / 43 | |
| 0.23.0 | 1 / 43 | |
| 0.22.0 | 1 / 43 | |
| 0.21.0 | 1 / 43 | |
| 0.20.0 | 1 / 43 | |
| 0.19.0 | 1 / 41 | |
| 0.18.0 | 1 / 41 | |
| 0.17.0 | 1 / 41 | |
| 0.16.0 | 1 / 41 | |
| 0.15.0 | 1 / 41 | |
| 0.14.5 | 1 / 41 | |
| 0.14.4 | 1 / 40 | |
| 0.14.3 | 1 / 40 | |
| 0.14.0 | 1 / 39 | |
| 0.13.0 | 1 / 39 | |
| 0.12.0 | 1 / 36 | |
| 0.11.0 | 1 / 32 | |
| 0.10.4 | 1 / 31 | |
| 0.10.3 | 1 / 31 | |
| 0.10.2 | 1 / 31 | |
| 0.10.1 | 1 / 31 | |
| 0.10.0 | 1 / 31 | |
| 0.9.0 | 1 / 30 | |
| 0.8.0 | 1 / 25 | |
| 0.7.0 | 1 / 23 | |
| 0.6.2 | 1 / 23 | |
| 0.6.1 | 1 / 23 | |
| 0.6.0 | 1 / 23 | |
| 0.5.4 | 1 / 23 | |
| 0.5.3 | 1 / 23 | |
| 0.5.2 | 1 / 23 | |
| 0.5.1 | 1 / 23 | |
| 0.5.0 | 1 / 23 | |
| 0.4.0 | 1 / 23 | |
| 0.3.1 | 1 / 22 | |
| 0.3.0 | 1 / 22 | |
| 0.2.2 | 1 / 22 | |
| 0.2.1 | 1 / 22 | |
| 0.2.0 | 1 / 23 | |
| 0.1.1 | 1 / 23 |
v0.37.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.37.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.36.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.35.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.35.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.35.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.15.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.