@paraspell/sdk
SDK for ParaSpell XCM/XCMP tool for developers
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| install-scripts | install-script:postinstall | AI (install-scripts): postinstall runs 'papi', the standard polkadot-api CLI for descriptor codegen; expected pattern for this package. | ai | |
| npm-metadata | url-dep:@polkadot-api/descriptors | AI (npm-metadata): file:.papi/descriptors is the standard papi codegen output; intentional local dep, not a supply-chain bypass. | ai | |
| dependencies | unvetted-dep:@polkadot-labs/hdkd | AI (dependencies): Standard Polkadot ecosystem library; stable dependency for this package. | ai | |
| dependencies | unvetted-dep:@polkadot-labs/hdkd-helpers | AI (dependencies): Standard Polkadot ecosystem library; stable dependency for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established package with 329 versions; lack of provenance is consistent across its history and not a risk signal here. | ai |
Versions (showing 51 of 74)
| Version | Deps | Published |
|---|---|---|
| 13.7.0 | 6 / 16 | |
| 13.6.0 | 6 / 16 | |
| 13.5.0 | 5 / 16 | |
| 13.4.1 | 5 / 16 | |
| 13.4.0 | 5 / 16 | |
| 13.3.0 | 5 / 16 | |
| 13.2.2 | 5 / 16 | |
| 13.2.1 | 5 / 16 | |
| 13.2.0 | 6 / 16 | |
| 13.1.0 | 6 / 16 | |
| 13.0.1 | 6 / 16 | |
| 13.0.0 | 6 / 16 | |
| 12.9.7 | 6 / 16 | |
| 12.9.6 | 6 / 16 | |
| 12.9.5 | 6 / 16 | |
| 12.9.4 | 6 / 16 | |
| 12.9.3 | 6 / 16 | |
| 12.9.2 | 6 / 16 | |
| 12.9.1 | 6 / 16 | |
| 12.9.0 | 6 / 16 | |
| 12.8.9 | 6 / 16 | |
| 12.8.8 | 6 / 16 | |
| 12.8.7 | 6 / 16 | |
| 12.8.6 | 6 / 16 | |
| 12.8.5 | 6 / 16 | |
| 12.8.4 | 6 / 16 | |
| 12.8.3 | 6 / 16 | |
| 12.8.2 | 6 / 16 | |
| 12.8.1 | 6 / 16 | |
| 12.8.0 | 6 / 16 | |
| 12.7.1 | 6 / 16 | |
| 12.7.0 | 6 / 16 | |
| 12.6.3 | 6 / 16 | |
| 12.6.1 | 6 / 16 | |
| 12.6.0 | 6 / 16 | |
| 12.5.1 | 6 / 16 | |
| 12.5.0 | 6 / 16 | |
| 12.4.0 | 6 / 16 | |
| 12.3.0 | 6 / 16 | |
| 12.2.2 | 6 / 15 | |
| 12.2.1 | 6 / 15 | |
| 12.2.0 | 6 / 15 | |
| 12.1.2 | 4 / 17 | |
| 12.1.1 | 4 / 17 | |
| 12.1.0 | 4 / 17 | |
| 12.0.6 | 4 / 17 | |
| 12.0.5 | 4 / 17 | |
| 12.0.4 | 4 / 17 | |
| 12.0.3 | 4 / 17 | |
| 12.0.2 | 4 / 17 | |
| 12.0.1 | 4 / 17 |
v13.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.2.0
2 findingsScript: papi
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.9.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.9.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.8.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.8.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.8.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.8.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.