@polkadot/rpc-rx
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): The 127.0.0.1 address appears only in a JSDoc code example showing local node connection; it is documentation, not a live network request. | ai | |
| dependencies | unvetted-dep:@types/rx | AI (dependencies): @types/rx is a TypeScript type declaration package; no runtime security risk for this package. | ai | |
| dependencies | unvetted-dep:@types/memoizee | AI (dependencies): @types/memoizee is a TypeScript type declaration package; no runtime security risk for this package. | ai | |
| phantom-deps | phantom-dep:@types/rx | AI (phantom-deps): Type-only dependency not directly imported at runtime; standard pattern in older TS projects. | ai | |
| phantom-deps | phantom-dep:@types/memoizee | AI (phantom-deps): Type-only dependency not directly imported at runtime; standard pattern in older TS projects. | ai |
Versions (showing 63 of 363)
| Version | Deps | Published |
|---|---|---|
| 0.31.63 | 5 / 0 | |
| 0.31.62 | 5 / 0 | |
| 0.31.61 | 5 / 0 | |
| 0.31.60 | 5 / 0 | |
| 0.31.59 | 5 / 0 | |
| 0.31.58 | 5 / 0 | |
| 0.31.57 | 5 / 0 | |
| 0.31.56 | 5 / 0 | |
| 0.31.55 | 5 / 0 | |
| 0.31.54 | 5 / 0 | |
| 0.31.53 | 5 / 0 | |
| 0.31.52 | 5 / 0 | |
| 0.31.51 | 5 / 0 | |
| 0.31.50 | 5 / 0 | |
| 0.31.49 | 5 / 0 | |
| 0.31.48 | 5 / 0 | |
| 0.31.47 | 5 / 0 | |
| 0.31.46 | 5 / 0 | |
| 0.31.45 | 5 / 0 | |
| 0.31.44 | 5 / 0 | |
| 0.31.43 | 5 / 0 | |
| 0.31.42 | 5 / 0 | |
| 0.31.41 | 5 / 0 | |
| 0.31.40 | 5 / 0 | |
| 0.31.39 | 5 / 0 | |
| 0.31.38 | 5 / 0 | |
| 0.31.37 | 5 / 0 | |
| 0.31.36 | 5 / 0 | |
| 0.31.35 | 5 / 0 | |
| 0.31.34 | 5 / 0 | |
| 0.31.33 | 5 / 0 | |
| 0.31.32 | 5 / 0 | |
| 0.31.31 | 5 / 0 | |
| 0.31.30 | 5 / 0 | |
| 0.31.29 | 5 / 0 | |
| 0.31.28 | 5 / 0 | |
| 0.31.27 | 5 / 0 | |
| 0.31.26 | 5 / 0 | |
| 0.31.25 | 5 / 0 | |
| 0.31.24 | 5 / 0 | |
| 0.31.23 | 5 / 0 | |
| 0.31.22 | 5 / 0 | |
| 0.31.21 | 5 / 0 | |
| 0.31.20 | 5 / 0 | |
| 0.31.19 | 5 / 0 | |
| 0.31.18 | 5 / 0 | |
| 0.31.17 | 5 / 0 | |
| 0.31.16 | 5 / 0 | |
| 0.31.15 | 5 / 0 | |
| 0.31.14 | 5 / 0 | |
| 0.31.13 | 5 / 0 | |
| 0.31.12 | 5 / 0 | |
| 0.31.11 | 5 / 0 | |
| 0.31.10 | 5 / 0 | |
| 0.31.9 | 5 / 0 | |
| 0.31.8 | 5 / 0 | |
| 0.31.7 | 5 / 0 | |
| 0.31.6 | 5 / 0 | |
| 0.31.5 | 5 / 0 | |
| 0.31.4 | 5 / 0 | |
| 0.31.3 | 5 / 0 | |
| 0.31.2 | 5 / 0 | |
| 0.31.1 | 5 / 0 |
v0.31.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.