@polkadot/types
Implementation of the Parity codec
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 |
|---|---|---|---|---|
| source-diff | large-new-source-files | AI (source-diff): @polkadot/types regularly adds new interface/type definition files as the Polkadot ecosystem evolves; this is expected growth for this package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require in CLI codegen scripts loads user-specified local type definitions via path.join(process.cwd(), ...). This is an intentional, safe pattern for a developer tooling script. | ai | |
| phantom-deps | phantom-dep:memoizee | AI (phantom-deps): memoizee is explicitly declared as a runtime dependency in package.json dependencies; the phantom-dep finding is a false positive for this package. | ai | |
| dependencies | unvetted-dep:@polkadot/types-augment | AI (dependencies): Sibling @polkadot org package from the same monorepo release; expected dependency. | ai | |
| dependencies | unvetted-dep:@polkadot/keyring | AI (dependencies): Sibling @polkadot org package; expected dependency for this monorepo package. Not a security risk. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Inflated semver reflects monorepo versioning convention; short README and no keywords are quality issues, not security signals. Legitimate paritytech-ci publisher. | ai | |
| phantom-deps | phantom-dep:@polkadot/types-augment | AI (phantom-deps): Used for TypeScript type augmentation in the polkadot-js monorepo; not a direct import by design. | ai | |
| dependencies | unvetted-dep:@polkadot/types-codec | AI (dependencies): Sibling @polkadot org package from the same monorepo release; expected dependency. | ai | |
| dependencies | unvetted-dep:@polkadot/types-create | AI (dependencies): Sibling @polkadot org package from the same monorepo release; expected dependency. | ai |
Versions (showing 100 of 723)
| Version | Deps | Published |
|---|---|---|
| 16.5.6 | 8 / 0 | |
| 16.5.4 | 8 / 0 | |
| 16.5.3 | 8 / 0 | |
| 16.5.2 | 8 / 0 | |
| 16.5.1 | 8 / 0 | |
| 16.4.9 | 8 / 0 | |
| 16.4.8 | 8 / 0 | |
| 16.4.7 | 8 / 0 | |
| 16.4.6 | 8 / 0 | |
| 16.4.5 | 8 / 0 | |
| 16.4.4 | 8 / 0 | |
| 16.4.3 | 8 / 0 | |
| 16.4.2 | 8 / 0 | |
| 16.4.1 | 8 / 0 | |
| 16.3.1 | 8 / 0 | |
| 16.2.2 | 8 / 0 | |
| 16.2.1 | 8 / 0 | |
| 16.1.2 | 8 / 0 | |
| 16.1.1 | 8 / 0 | |
| 16.0.1 | 8 / 0 | |
| 15.10.2 | 8 / 0 | |
| 15.10.1 | 8 / 0 | |
| 15.9.3 | 8 / 0 | |
| 15.9.2 | 8 / 0 | |
| 15.9.1 | 8 / 0 | |
| 15.8.1 | 8 / 0 | |
| 15.7.2 | 8 / 0 | |
| 15.7.1 | 8 / 0 | |
| 15.6.1 | 8 / 0 | |
| 15.5.2 | 8 / 0 | |
| 15.5.1 | 8 / 0 | |
| 15.4.1 | 8 / 0 | |
| 15.3.1 | 8 / 0 | |
| 15.2.1 | 8 / 0 | |
| 15.1.1 | 8 / 0 | |
| 15.0.2 | 8 / 0 | |
| 15.0.1 | 8 / 0 | |
| 14.3.1 | 8 / 0 | |
| 14.2.3 | 8 / 0 | |
| 14.2.2 | 8 / 0 | |
| 14.2.1 | 8 / 0 | |
| 14.1.1 | 8 / 0 | |
| 14.0.1 | 8 / 0 | |
| 13.2.1 | 8 / 0 | |
| 13.1.1 | 8 / 0 | |
| 13.0.1 | 8 / 0 | |
| 12.4.2 | 8 / 0 | |
| 12.4.1 | 8 / 0 | |
| 12.3.1 | 8 / 0 | |
| 12.2.3 | 8 / 0 | |
| 12.2.2 | 8 / 0 | |
| 12.2.1 | 8 / 0 | |
| 12.1.1 | 8 / 0 | |
| 12.0.2 | 8 / 0 | |
| 12.0.1 | 8 / 0 | |
| 11.3.1 | 8 / 0 | |
| 11.2.1 | 8 / 0 | |
| 11.1.1 | 8 / 0 | |
| 11.0.3 | 8 / 0 | |
| 11.0.2 | 8 / 0 | |
| 11.0.1 | 8 / 0 | |
| 10.13.1 | 8 / 0 | |
| 10.12.6 | 8 / 0 | |
| 10.12.4 | 8 / 0 | |
| 10.12.3 | 8 / 0 | |
| 10.12.2 | 8 / 0 | |
| 10.12.1 | 8 / 0 | |
| 10.11.3 | 8 / 0 | |
| 10.11.2 | 8 / 0 | |
| 10.11.1 | 8 / 0 | |
| 10.10.1 | 8 / 0 | |
| 10.9.1 | 8 / 0 | |
| 10.8.1 | 8 / 0 | |
| 10.7.3 | 8 / 0 | |
| 10.7.2 | 8 / 0 | |
| 10.7.1 | 8 / 0 | |
| 10.6.1 | 8 / 0 | |
| 10.5.1 | 8 / 0 | |
| 10.4.1 | 8 / 0 | |
| 10.3.4 | 8 / 0 | |
| 10.3.3 | 8 / 0 | |
| 10.3.2 | 8 / 0 | |
| 10.3.1 | 8 / 0 | |
| 10.2.2 | 8 / 0 | |
| 10.2.1 | 8 / 0 | |
| 10.1.4 | 8 / 0 | |
| 10.1.3 | 8 / 0 | |
| 10.1.2 | 8 / 0 | |
| 10.1.1 | 8 / 0 | |
| 10.0.1 | 8 / 0 | |
| 9.14.2 | 8 / 0 | |
| 9.14.1 | 8 / 0 | |
| 9.13.6 | 8 / 0 | |
| 9.13.5 | 8 / 0 | |
| 9.13.4 | 8 / 0 | |
| 9.13.2 | 8 / 0 | |
| 9.13.1 | 8 / 0 | |
| 9.12.1 | 8 / 0 | |
| 9.11.3 | 8 / 0 | |
| 9.11.2 | 8 / 0 |
v16.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.12.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.12.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.12.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.14.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.13.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.13.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.13.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.