@buildonspark/lrc20-sdk
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 |
|---|---|---|---|---|
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding is standard Bitcoin pubkey/txid handling in a crypto SDK; not a malicious payload pattern. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Raw IPs are localhost and sslip.io-wrapped testnet/devnet endpoints in constants.ts — expected for a blockchain SDK. | ai | |
| phantom-deps | phantom-dep:stream | AI (phantom-deps): Explicitly ignored in depcheck config; used as browser polyfill shim, not a direct import. | ai | |
| phantom-deps | phantom-dep:ts-proto | AI (phantom-deps): Explicitly ignored in depcheck config; used as a build-time code generator, not a direct import. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.0.63 | 12 / 14 | |
| 0.0.62 | 12 / 14 | |
| 0.0.61 | 12 / 14 | |
| 0.0.60 | 12 / 14 | |
| 0.0.59 | 12 / 14 | |
| 0.0.58 | 12 / 14 | |
| 0.0.57 | 12 / 14 | |
| 0.0.56 | 13 / 14 | |
| 0.0.55 | 13 / 14 | |
| 0.0.54 | 10 / 14 | |
| 0.0.53 | 10 / 14 | |
| 0.0.52 | 10 / 14 | |
| 0.0.51 | 16 / 16 | |
| 0.0.50 | 16 / 16 |
v0.0.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.