@polkadot/api
Promise and RxJS wrappers around the Polkadot JS RPC
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): paritytech-ci is Parity Technologies' CI account (1999 approvals, 1549 days old); legitimate org-level publisher transition for @polkadot scope. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): paritytech-ci is the established Parity CI publisher for @polkadot packages; maintainer addition is a legitimate organizational change. | ai | |
| dependencies | unvetted-dep:@polkadot/api-metadata | AI (dependencies): @polkadot/api-metadata is a sibling package in the same polkadot-js monorepo, published by the same trusted maintainer (jacogr). This is a stable intra-org dependency, not a supply chain risk. | ai | |
| dependencies | unvetted-dep:@types/rx | AI (dependencies): @types/rx is a legitimate TypeScript type definition package for RxJS; expected dependency for this RxJS-based Polkadot API wrapper. | ai | |
| phantom-deps | phantom-dep:@types/rx | AI (phantom-deps): @types/rx is a TypeScript type declaration package loaded by convention; phantom-dep finding is a stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@polkadot/rpc-rx | AI (dependencies): @polkadot/rpc-rx is a sibling package in the official Polkadot JS ecosystem, published by the same trusted maintainer (jacogr). | ai | |
| dependencies | unvetted-dep:@polkadot/api-jsonrpc | AI (dependencies): First-party sibling package in the @polkadot monorepo, published by the same trusted maintainer at matching version constraints. | ai | |
| dependencies | unvetted-dep:@polkadot/api-format | AI (dependencies): First-party @polkadot/* scoped package from the same trusted publisher (jacogr). Not a third-party risk. | ai | |
| dependencies | unvetted-dep:@polkadot/params | AI (dependencies): First-party @polkadot/* scoped package from the same trusted publisher (jacogr). Not a third-party risk. | ai | |
| dependencies | unvetted-dep:@polkadot/jsonrpc | AI (dependencies): First-party @polkadot/* scoped package from the same trusted publisher (jacogr). Not a third-party risk. | ai | |
| dependencies | unvetted-dep:@polkadot/api-provider | AI (dependencies): First-party @polkadot/* scoped package from the same trusted publisher (jacogr). Not a third-party risk. | ai | |
| phantom-deps | phantom-dep:@polkadot/api-provider | AI (phantom-deps): Phantom dep is a sibling package in the same @polkadot monorepo scope; this is a known packaging pattern for this org and not a security concern. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance by years; 228k weekly downloads and 3082-day history confirm legitimacy without attestation. | ai | |
| phantom-deps | phantom-dep:@polkadot/types-create | AI (phantom-deps): Sibling monorepo package; declared as dependency for transitive use, common pattern in polkadot-js monorepo. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): 127.0.0.1:9933/9944 are localhost default URLs for a local Substrate/Polkadot node — standard dev config for a blockchain API library, not malicious. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): @polkadot/api is a major blockchain SDK from Parity Technologies, not a typosquat of 'ajv'. Levenshtein match is a false positive. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): @polkadot/api is a major blockchain SDK from Parity Technologies, not a typosquat of 'joi'. Levenshtein match is a false positive. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): @polkadot/api is a major blockchain SDK from Parity Technologies, not a typosquat of 'pg'. Levenshtein match is a false positive. | ai | |
| typosquat | typosquat.levenshtein:hapi | AI (typosquat): @polkadot/api is a major blockchain SDK from Parity Technologies, not a typosquat of 'hapi'. Scoped package with completely different purpose. | ai | |
| phantom-deps | phantom-dep:@polkadot/types-augment | AI (phantom-deps): Sibling monorepo package; declared as dependency for transitive use, common pattern in polkadot-js monorepo. | ai |
Versions (showing 100 of 951)
| Version | Deps | Published |
|---|---|---|
| 16.5.6 | 17 / 0 | |
| 16.5.4 | 17 / 0 | |
| 16.5.3 | 17 / 0 | |
| 16.5.2 | 17 / 0 | |
| 16.5.1 | 17 / 0 | |
| 16.4.9 | 17 / 0 | |
| 16.4.8 | 17 / 0 | |
| 16.4.7 | 17 / 0 | |
| 16.4.6 | 17 / 0 | |
| 16.4.5 | 17 / 0 | |
| 16.4.4 | 17 / 0 | |
| 16.4.3 | 17 / 0 | |
| 16.4.2 | 17 / 0 | |
| 16.4.1 | 17 / 0 | |
| 16.3.1 | 17 / 0 | |
| 16.2.2 | 17 / 0 | |
| 16.2.1 | 17 / 0 | |
| 16.1.2 | 17 / 0 | |
| 16.1.1 | 17 / 0 | |
| 16.0.1 | 17 / 0 | |
| 15.10.2 | 17 / 0 | |
| 15.10.1 | 17 / 0 | |
| 15.9.3 | 17 / 0 | |
| 15.9.2 | 17 / 0 | |
| 15.9.1 | 17 / 0 | |
| 15.8.1 | 17 / 0 | |
| 15.7.2 | 17 / 0 | |
| 15.7.1 | 17 / 0 | |
| 15.6.1 | 17 / 0 | |
| 15.5.2 | 17 / 0 | |
| 15.5.1 | 17 / 0 | |
| 15.4.1 | 17 / 0 | |
| 15.3.1 | 17 / 0 | |
| 15.2.1 | 17 / 0 | |
| 15.1.1 | 17 / 0 | |
| 15.0.2 | 17 / 0 | |
| 15.0.1 | 17 / 0 | |
| 14.3.1 | 17 / 0 | |
| 14.2.3 | 17 / 0 | |
| 14.2.2 | 17 / 0 | |
| 14.2.1 | 17 / 0 | |
| 14.1.1 | 17 / 0 | |
| 14.0.1 | 17 / 0 | |
| 13.2.1 | 17 / 0 | |
| 13.1.1 | 17 / 0 | |
| 13.0.1 | 17 / 0 | |
| 12.4.2 | 17 / 0 | |
| 12.4.1 | 17 / 0 | |
| 12.3.1 | 17 / 0 | |
| 12.2.3 | 17 / 0 | |
| 12.2.2 | 17 / 0 | |
| 12.2.1 | 17 / 0 | |
| 12.1.1 | 17 / 0 | |
| 12.0.2 | 17 / 0 | |
| 12.0.1 | 17 / 0 | |
| 11.3.1 | 17 / 0 | |
| 11.2.1 | 17 / 0 | |
| 11.1.1 | 17 / 0 | |
| 11.0.3 | 17 / 0 | |
| 11.0.2 | 17 / 0 | |
| 11.0.1 | 17 / 0 | |
| 10.13.1 | 17 / 0 | |
| 10.12.6 | 17 / 0 | |
| 10.12.5 | 17 / 0 | |
| 10.12.4 | 17 / 0 | |
| 10.12.3 | 17 / 0 | |
| 10.12.2 | 17 / 0 | |
| 10.12.1 | 17 / 0 | |
| 10.11.3 | 17 / 0 | |
| 10.11.2 | 17 / 0 | |
| 10.11.1 | 17 / 0 | |
| 10.10.1 | 17 / 0 | |
| 10.9.1 | 17 / 0 | |
| 10.8.1 | 17 / 0 | |
| 10.7.3 | 17 / 0 | |
| 10.7.2 | 17 / 0 | |
| 10.7.1 | 17 / 0 | |
| 10.6.1 | 17 / 0 | |
| 10.5.1 | 17 / 0 | |
| 10.4.1 | 17 / 0 | |
| 10.3.4 | 17 / 0 | |
| 10.3.3 | 17 / 0 | |
| 10.3.2 | 17 / 0 | |
| 10.3.1 | 17 / 0 | |
| 10.2.2 | 17 / 0 | |
| 10.2.1 | 17 / 0 | |
| 10.1.4 | 17 / 0 | |
| 10.1.3 | 17 / 0 | |
| 10.1.2 | 17 / 0 | |
| 10.1.1 | 17 / 0 | |
| 10.0.1 | 17 / 0 | |
| 9.14.2 | 17 / 0 | |
| 9.14.1 | 17 / 0 | |
| 9.13.6 | 17 / 0 | |
| 9.13.5 | 17 / 0 | |
| 9.13.4 | 17 / 0 | |
| 9.13.3 | 17 / 0 | |
| 9.13.2 | 17 / 0 | |
| 9.13.1 | 17 / 0 | |
| 9.12.1 | 17 / 0 |
v16.5.6
2 findingsThis version was published by a different npm account than previous versions on 2026-03-23. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.4.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.12.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.12.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.12.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.12.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.12.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.11.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.14.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.14.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.13.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.13.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.13.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.13.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.13.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.