@crossmint/common-sdk-base
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-removed | AI (maintainer-change): Paired with legitimate add; consistent with org maintainer turnover. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Routine Crossmint team maintainer rotation, no compromise indicators. | ai | |
| provenance | missing-githead | AI (provenance): Publish tooling variance in monorepo CI, not a regression to malicious behavior. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by CI/CD migration; SLSA provenance confirms legitimate publish pipeline. | ai | |
| provenance | publisher-changed | AI (provenance): Crossmint migrated publishing to GitHub Actions CI/CD with SLSA attestation; this is a documented org-level CI transition. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): viem and @solana/web3.js are canonical blockchain libs; addition is consistent with Crossmint SDK's multi-chain scope. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Long-standing package with no description; not a malice indicator for this established SDK. | ai |
Versions (showing 51 of 51)
| Version | Deps | Published |
|---|---|---|
| 0.11.0 | 4 / 1 | |
| 0.10.2 | 4 / 1 | |
| 0.10.1 | 4 / 1 | |
| 0.10.0 | 4 / 1 | |
| 0.9.20 | 4 / 1 | |
| 0.9.19 | 4 / 1 | |
| 0.9.18 | 4 / 1 | |
| 0.9.17 | 4 / 1 | |
| 0.9.16 | 4 / 1 | |
| 0.9.15 | 4 / 1 | |
| 0.9.14 | 4 / 1 | |
| 0.9.13 | 4 / 1 | |
| 0.9.12 | 4 / 1 | |
| 0.9.11 | 4 / 1 | |
| 0.9.10 | 4 / 1 | |
| 0.9.8 | 4 / 1 | |
| 0.9.7 | 4 / 1 | |
| 0.9.6 | 4 / 1 | |
| 0.9.5 | 4 / 1 | |
| 0.9.4 | 4 / 1 | |
| 0.9.3 | 4 / 1 | |
| 0.9.2 | 4 / 1 | |
| 0.9.1 | 4 / 1 | |
| 0.9.0 | 4 / 1 | |
| 0.8.5 | 4 / 1 | |
| 0.8.4 | 4 / 1 | |
| 0.8.3 | 4 / 1 | |
| 0.8.2 | 4 / 1 | |
| 0.8.1 | 4 / 1 | |
| 0.8.0 | 4 / 1 | |
| 0.7.2 | 2 / 1 | |
| 0.7.1 | 2 / 1 | |
| 0.7.0 | 2 / 1 | |
| 0.6.0 | 2 / 1 | |
| 0.5.1 | 2 / 1 | |
| 0.5.0 | 2 / 1 | |
| 0.4.2 | 2 / 1 | |
| 0.4.1 | 2 / 1 | |
| 0.4.0 | 2 / 1 | |
| 0.3.4 | 2 / 1 | |
| 0.3.3 | 2 / 1 | |
| 0.3.2 | 2 / 1 | |
| 0.3.1 | 2 / 1 | |
| 0.3.0 | 2 / 1 | |
| 0.2.0 | 2 / 1 | |
| 0.1.4 | 2 / 1 | |
| 0.1.3 | 2 / 1 | |
| 0.1.2 | 2 / 1 | |
| 0.1.1 | 2 / 1 | |
| 0.1.0 | 2 / 1 | |
| 0.0.13 | 2 / 1 |
v0.11.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: maxwellfortney.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: maxwellfortney.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: maxwellfortney.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: maxwellfortney.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: maxwellfortney.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: maxwellfortney.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: maxwellfortney.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: maxwellfortney.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: maxwellfortney.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: maxwellfortney.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: maxwellfortney.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.