@rango-dev/signer-solana
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established package with 133 versions; lack of provenance is consistent across all releases and not a new risk. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 0.48.0 | 4 / 1 | |
| 0.47.1 | 4 / 1 | |
| 0.47.0 | 4 / 1 | |
| 0.46.1 | 4 / 1 | |
| 0.44.0 | 4 / 1 | |
| 0.43.0 | 4 / 1 | |
| 0.42.0 | 4 / 1 | |
| 0.41.0 | 4 / 1 | |
| 0.40.0 | 4 / 1 | |
| 0.39.0 | 4 / 1 | |
| 0.38.0 | 4 / 1 | |
| 0.37.0 | 4 / 1 | |
| 0.36.0 | 4 / 1 | |
| 0.35.0 | 4 / 1 | |
| 0.34.0 | 4 / 1 | |
| 0.33.0 | 4 / 1 | |
| 0.32.0 | 4 / 1 | |
| 0.31.0 | 3 / 1 | |
| 0.30.0 | 3 / 1 | |
| 0.29.0 | 3 / 1 | |
| 0.28.0 | 3 / 1 |
v0.38.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.28.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.