@polkadot/util
A collection of useful utilities for @polkadot
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@types/camelcase | AI (dependencies): @types/camelcase is the TypeScript type definitions for the well-known camelcase package; it is benign and consistent with this package's pattern of listing @types/* as runtime deps. | ai | |
| phantom-deps | phantom-dep:@types/camelcase | AI (phantom-deps): Listing @types/* packages as runtime deps without direct imports is a known pattern in this Polkadot TypeScript package; other @types/* phantom deps are already accepted. | ai | |
| phantom-deps | phantom-dep:@types/ip-regex | AI (phantom-deps): @types packages are TypeScript type declarations consumed by tooling, not direct imports; phantom-dep firing on them is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/xxhashjs | AI (phantom-deps): @types packages are TypeScript type declarations consumed by tooling, not direct imports; phantom-dep firing on them is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/deasync | AI (phantom-deps): @types packages are TypeScript type declarations consumed by tooling, not direct imports; phantom-dep firing on them is a stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@types/ip-regex | AI (dependencies): @types/ip-regex is a DefinitelyTyped TypeScript type definition package — benign by nature, no runtime code execution risk. | ai | |
| dependencies | unvetted-dep:@types/xxhashjs | AI (dependencies): @types/xxhashjs is a DefinitelyTyped TypeScript type definition package — benign by nature, no runtime code execution risk. | ai | |
| provenance | missing-githead | AI (provenance): Package is from a highly trusted publisher (jacogr, 8095 approved/0 rejected) with a 3000+ day history. Missing gitHead reflects a publish environment change, not a security concern for this package. | ai | |
| source-diff | large-new-source-files | AI (source-diff): @polkadot/util is an actively developed utility library; adding new source files across minor versions is expected organic growth, not injected code. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): bn.js and keccak are well-established cryptographic libraries appropriate for a blockchain utility package; their addition is expected and legitimate. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase reflects legitimate addition of crypto utilities (bn.js, keccak wrappers) in a growing blockchain utility library from a trusted publisher. | ai | |
| dependencies | unvetted-dep:keccak | AI (dependencies): keccak is a well-known cryptographic hash library standard in the blockchain/Ethereum ecosystem; legitimate dependency for @polkadot/util. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance adoption; publisher has 8083 approved packages and strong trust history. Not a meaningful risk signal here. | ai | |
| phantom-deps | phantom-dep:babel-runtime | AI (phantom-deps): babel-runtime is a legitimate runtime dependency used via babel-plugin-transform-runtime (Babel 6 pattern); not a phantom dep for this package. | ai | |
| provenance | publisher-changed | AI (provenance): paritytech-ci is Parity Technologies' CI publishing account with 111 approved packages; the polkadotjs→paritytech-ci transition is a known organizational consolidation, not a compromise. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): paritytech-ci is a verified Parity Technologies CI account with strong track record; addition is a legitimate organizational change. | ai | |
| phantom-deps | phantom-dep:@types/bn.js | AI (phantom-deps): @types/bn.js is a TypeScript type definition used by convention in the polkadot-js ecosystem; phantom dep finding is a stable false positive here. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding is core functionality of @polkadot/util; Buffer.from(value, 'hex') is a standard, non-obfuscated utility operation. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): @polkadot/util is a well-known Polkadot ecosystem utility library, not a typosquat of uuid. The name similarity is purely coincidental. | ai |
Versions (showing 100 of 551)
| Version | Deps | Published |
|---|---|---|
| 0.32.6 | 12 / 0 | |
| 0.32.5 | 12 / 0 | |
| 0.32.4 | 12 / 0 | |
| 0.32.3 | 12 / 0 | |
| 0.32.2 | 12 / 0 | |
| 0.32.1 | 12 / 0 | |
| 0.31.7 | 12 / 0 | |
| 0.31.6 | 12 / 0 | |
| 0.31.5 | 12 / 0 | |
| 0.31.4 | 12 / 0 | |
| 0.31.3 | 12 / 0 | |
| 0.31.2 | 12 / 0 | |
| 0.31.1 | 12 / 0 | |
| 0.30.7 | 12 / 0 | |
| 0.30.6 | 12 / 0 | |
| 0.30.4 | 10 / 0 | |
| 0.30.3 | 10 / 0 | |
| 0.30.2 | 10 / 0 | |
| 0.30.1 | 10 / 0 | |
| 0.29.33 | 10 / 0 | |
| 0.29.32 | 10 / 0 | |
| 0.29.31 | 10 / 0 | |
| 0.29.30 | 10 / 0 | |
| 0.29.29 | 10 / 0 | |
| 0.29.28 | 10 / 0 | |
| 0.29.27 | 10 / 0 | |
| 0.29.26 | 10 / 0 | |
| 0.29.25 | 10 / 0 | |
| 0.29.24 | 10 / 0 | |
| 0.29.23 | 10 / 0 | |
| 0.29.22 | 10 / 0 | |
| 0.29.21 | 10 / 0 | |
| 0.29.20 | 10 / 0 | |
| 0.29.19 | 10 / 0 | |
| 0.29.18 | 10 / 0 | |
| 0.29.17 | 10 / 0 | |
| 0.29.16 | 10 / 0 | |
| 0.29.15 | 10 / 0 | |
| 0.29.14 | 10 / 0 | |
| 0.29.13 | 10 / 0 | |
| 0.29.12 | 10 / 0 | |
| 0.29.11 | 10 / 0 | |
| 0.29.10 | 10 / 0 | |
| 0.29.9 | 10 / 0 | |
| 0.29.8 | 10 / 0 | |
| 0.29.7 | 10 / 0 | |
| 0.29.6 | 10 / 0 | |
| 0.29.5 | 10 / 0 | |
| 0.29.4 | 10 / 0 | |
| 0.29.3 | 10 / 0 | |
| 0.29.2 | 10 / 0 | |
| 0.29.1 | 10 / 0 | |
| 0.28.25 | 10 / 0 | |
| 0.28.24 | 10 / 0 | |
| 0.28.23 | 10 / 0 | |
| 0.28.22 | 10 / 0 | |
| 0.28.21 | 10 / 0 | |
| 0.28.20 | 10 / 0 | |
| 0.28.19 | 10 / 0 | |
| 0.28.18 | 10 / 0 | |
| 0.28.17 | 10 / 0 | |
| 0.28.16 | 10 / 0 | |
| 0.28.15 | 10 / 0 | |
| 0.28.14 | 10 / 0 | |
| 0.28.13 | 10 / 0 | |
| 0.28.12 | 10 / 0 | |
| 0.28.11 | 10 / 0 | |
| 0.28.10 | 10 / 0 | |
| 0.28.9 | 10 / 0 | |
| 0.28.8 | 10 / 0 | |
| 0.28.7 | 10 / 0 | |
| 0.28.6 | 10 / 0 | |
| 0.28.5 | 10 / 0 | |
| 0.28.4 | 10 / 0 | |
| 0.28.3 | 10 / 0 | |
| 0.28.2 | 10 / 0 | |
| 0.28.1 | 10 / 0 | |
| 0.27.12 | 10 / 0 | |
| 0.27.11 | 10 / 0 | |
| 0.27.10 | 10 / 0 | |
| 0.27.9 | 10 / 0 | |
| 0.27.1 | 10 / 0 | |
| 0.26.36 | 10 / 0 | |
| 0.26.35 | 10 / 0 | |
| 0.26.34 | 10 / 0 | |
| 0.26.33 | 10 / 0 | |
| 0.26.32 | 10 / 0 | |
| 0.26.31 | 10 / 0 | |
| 0.26.30 | 10 / 0 | |
| 0.26.29 | 9 / 0 | |
| 0.26.27 | 9 / 0 | |
| 0.26.26 | 9 / 0 | |
| 0.26.25 | 9 / 0 | |
| 0.26.24 | 9 / 0 | |
| 0.26.23 | 9 / 0 | |
| 0.26.22 | 9 / 0 | |
| 0.26.21 | 9 / 0 | |
| 0.26.20 | 9 / 0 | |
| 0.26.19 | 9 / 0 | |
| 0.26.18 | 9 / 0 |
v0.32.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.
v0.32.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.
v0.32.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.
v0.32.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.
v0.32.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.
v0.32.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.
v0.31.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.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.
v0.31.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.
v0.31.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.
v0.31.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.
v0.31.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.
v0.31.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.
v0.30.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.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.
v0.30.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.