@polkadot/x-bigint
A cross-environment BigInt replacement
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 the established Parity Technologies CI account (83 approved packages, 563 days history); transition from polkadotjs is a known organizational publishing shift for the polkadot-js ecosystem. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): paritytech-ci is a well-established publisher account for the Polkadot ecosystem; this is a legitimate organizational maintainer transition. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit dependency for TypeScript transpilation; stable for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo utility package with coordinated versioning; short README and inflated semver are expected patterns, not spam indicators. | ai | |
| dependencies | unvetted-dep:@polkadot/x-global | AI (dependencies): Sibling package within the same monorepo; coordinated versioning is expected and safe. | ai |
Versions (showing 85 of 85)
| Version | Deps | Published |
|---|---|---|
| 14.0.3 | 2 / 0 | |
| 14.0.2 | 2 / 0 | |
| 14.0.1 | 2 / 0 | |
| 13.5.9 | 2 / 0 | |
| 13.5.8 | 2 / 0 | |
| 13.5.7 | 2 / 0 | |
| 13.5.6 | 2 / 0 | |
| 13.5.5 | 2 / 0 | |
| 13.5.4 | 2 / 0 | |
| 13.5.3 | 2 / 0 | |
| 13.5.2 | 2 / 0 | |
| 13.5.1 | 2 / 0 | |
| 13.4.4 | 2 / 0 | |
| 13.4.3 | 2 / 0 | |
| 13.4.2 | 2 / 0 | |
| 13.4.1 | 2 / 0 | |
| 13.3.1 | 2 / 0 | |
| 13.2.3 | 2 / 0 | |
| 13.2.2 | 2 / 0 | |
| 13.2.1 | 2 / 0 | |
| 13.1.1 | 2 / 0 | |
| 13.0.2 | 2 / 0 | |
| 13.0.1 | 2 / 0 | |
| 12.6.2 | 2 / 0 | |
| 12.6.1 | 2 / 0 | |
| 12.5.1 | 2 / 0 | |
| 12.4.2 | 2 / 0 | |
| 12.4.1 | 2 / 0 | |
| 12.3.2 | 2 / 0 | |
| 12.3.1 | 2 / 0 | |
| 12.2.2 | 2 / 0 | |
| 12.2.1 | 2 / 0 | |
| 12.1.2 | 2 / 0 | |
| 12.1.1 | 2 / 0 | |
| 12.0.1 | 2 / 0 | |
| 11.1.3 | 2 / 0 | |
| 11.1.2 | 2 / 0 | |
| 11.1.1 | 2 / 0 | |
| 11.0.2 | 2 / 0 | |
| 11.0.1 | 2 / 0 | |
| 10.4.2 | 2 / 0 | |
| 10.4.1 | 2 / 0 | |
| 10.3.1 | 2 / 0 | |
| 10.2.6 | 2 / 0 | |
| 10.2.5 | 2 / 0 | |
| 10.2.4 | 2 / 0 | |
| 10.2.3 | 2 / 0 | |
| 10.2.2 | 2 / 0 | |
| 10.2.1 | 2 / 0 | |
| 10.1.14 | 2 / 0 | |
| 10.1.13 | 2 / 0 | |
| 10.1.12 | 2 / 0 | |
| 10.1.11 | 2 / 0 | |
| 10.1.10 | 2 / 0 | |
| 10.1.9 | 2 / 0 | |
| 10.1.8 | 2 / 0 | |
| 10.1.7 | 2 / 0 | |
| 10.1.6 | 2 / 0 | |
| 10.1.5 | 2 / 0 | |
| 10.1.4 | 2 / 0 | |
| 10.1.3 | 2 / 0 | |
| 10.1.2 | 2 / 0 | |
| 10.1.1 | 2 / 0 | |
| 10.0.2 | 2 / 0 | |
| 10.0.1 | 2 / 0 | |
| 9.7.2 | 2 / 0 | |
| 9.7.1 | 2 / 0 | |
| 9.6.2 | 2 / 0 | |
| 9.6.1 | 2 / 0 | |
| 9.5.1 | 2 / 0 | |
| 9.4.1 | 2 / 0 | |
| 9.3.1 | 2 / 0 | |
| 9.2.1 | 2 / 0 | |
| 9.1.1 | 2 / 0 | |
| 9.0.1 | 2 / 0 | |
| 8.7.1 | 2 / 0 | |
| 8.6.1 | 2 / 0 | |
| 8.5.1 | 2 / 0 | |
| 8.4.1 | 2 / 0 | |
| 8.3.3 | 2 / 0 | |
| 8.3.2 | 2 / 0 | |
| 8.3.1 | 2 / 0 | |
| 8.2.2 | 2 / 0 | |
| 8.1.2 | 2 / 0 | |
| 8.1.1 | 2 / 0 |
v14.0.2
2 findingsThis version was published by a different npm account than previous versions on 2026-03-16. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.5.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.5.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.2.2
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.5.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.2
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.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.2
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.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.2
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. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.