@leather.io/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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package @leather.io/rpc; Levenshtein match to 'pg' is a false positive with no brand overlap. | ai | |
| phantom-deps | phantom-dep:@stacks/network | AI (phantom-deps): Listed as runtime dep; used transitively via @leather.io/stacks — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@scure/btc-signer | AI (phantom-deps): Listed as runtime dep; referenced in config files — stable false positive for this package. | ai |
Versions (showing 51 of 53)
| Version | Deps | Published |
|---|---|---|
| 2.21.16 | 7 / 5 | |
| 2.21.15 | 7 / 5 | |
| 2.21.14 | 7 / 5 | |
| 2.21.13 | 7 / 5 | |
| 2.21.12 | 7 / 5 | |
| 2.21.11 | 7 / 5 | |
| 2.21.10 | 7 / 5 | |
| 2.21.9 | 7 / 5 | |
| 2.21.8 | 7 / 5 | |
| 2.21.7 | 7 / 5 | |
| 2.21.6 | 7 / 5 | |
| 2.21.4 | 7 / 5 | |
| 2.21.3 | 7 / 5 | |
| 2.21.2 | 7 / 5 | |
| 2.21.1 | 7 / 2 | |
| 2.21.0 | 7 / 2 | |
| 2.20.24 | 7 / 2 | |
| 2.20.23 | 7 / 2 | |
| 2.20.22 | 7 / 2 | |
| 2.20.21 | 7 / 2 | |
| 2.20.20 | 7 / 2 | |
| 2.20.19 | 7 / 2 | |
| 2.20.18 | 7 / 2 | |
| 2.20.17 | 7 / 2 | |
| 2.20.16 | 7 / 2 | |
| 2.20.15 | 7 / 2 | |
| 2.20.14 | 7 / 2 | |
| 2.20.13 | 7 / 2 | |
| 2.20.12 | 7 / 2 | |
| 2.20.11 | 7 / 2 | |
| 2.20.10 | 7 / 2 | |
| 2.20.9 | 7 / 2 | |
| 2.20.8 | 6 / 2 | |
| 2.20.7 | 6 / 2 | |
| 2.20.6 | 6 / 2 | |
| 2.20.5 | 6 / 2 | |
| 2.20.4 | 6 / 2 | |
| 2.20.3 | 6 / 2 | |
| 2.20.2 | 6 / 2 | |
| 2.20.1 | 6 / 2 | |
| 2.20.0 | 6 / 2 | |
| 2.18.0 | 6 / 2 | |
| 2.17.0 | 6 / 2 | |
| 2.16.6 | 6 / 2 | |
| 2.16.5 | 6 / 2 | |
| 2.16.4 | 6 / 2 | |
| 2.16.3 | 6 / 2 | |
| 2.16.2 | 6 / 2 | |
| 2.16.1 | 6 / 2 | |
| 2.16.0 | 6 / 2 | |
| 2.15.0 | 6 / 2 |
v2.21.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.20.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.20.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.