@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 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 2.2.5 | 7 / 1 | |
| 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 | |
| 2.1.7 | 7 / 1 | |
| 2.1.6 | 7 / 1 | |
| 2.1.5 | 7 / 1 | |
| 2.1.4 | 7 / 1 | |
| 2.1.3 | 7 / 1 | |
| 2.1.2 | 7 / 1 | |
| 2.1.1 | 7 / 1 | |
| 2.1.0 | 6 / 0 | |
| 2.0.1 | 2 / 0 | |
| 2.0.0 | 2 / 0 |
v2.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.