@chainflip/solana
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Monorepo package; missing description is benign given SLSA provenance and legitimate repo. | ai | |
| dependencies | unvetted-dep:@chainflip/scale | AI (dependencies): First-party sibling dep from chainflip-io org; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@chainflip/utils | AI (dependencies): First-party sibling dep from chainflip-io org; stable pattern across all versions. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 2.2.3 | 7 / 1 | |
| 2.2.2 | 7 / 1 | |
| 2.2.1 | 7 / 1 | |
| 2.2.0 | 7 / 1 | |
| 2.1.9 | 7 / 1 | |
| 2.1.8 | 7 / 1 |
v2.2.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.