@hiero-ledger/proto
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): Publisher changed from human account to GitHub Actions CI/CD with SLSA provenance attestation — this is a supply chain security improvement, not a compromise indicator. | ai | |
| phantom-deps | phantom-dep:rimraf | AI (phantom-deps): rimraf is a well-established utility; its presence as a phantom dep indicates a packaging quality issue (should be devDep), not a security risk. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 2.30.0 | 2 / 29 | |
| 2.29.0 | 2 / 29 | |
| 2.28.0 | 2 / 29 | |
| 2.27.0 | 2 / 29 | |
| 2.25.0 | 1 / 29 | |
| 2.24.0 | 1 / 29 | |
| 2.23.0 | 1 / 29 | |
| 2.22.0 | 2 / 29 | |
| 2.21.0 | 2 / 29 |
v2.30.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.28.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.27.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-27. 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.
v2.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.