← Home

@buildonspark/lrc20-sdk

npm Homepage
43
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

mgorven.lscoreymartincpartee6ch-brianbrett.lslightsparkmaxvijayar

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 43 of 43)

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
0.0.49 16 / 16
0.0.48 16 / 16
0.0.47 16 / 16
0.0.46 16 / 16
0.0.45 16 / 16
0.0.44 16 / 16
0.0.43 16 / 16
0.0.42 16 / 16
0.0.41 16 / 16
0.0.40 16 / 16
0.0.39 16 / 16
0.0.38 16 / 16
0.0.37 16 / 16
0.0.36 16 / 16
0.0.35 16 / 16
0.0.34 16 / 16
0.0.33 16 / 16
0.0.32 16 / 14
0.0.31 16 / 14
0.0.30 16 / 14
0.0.29 16 / 14
0.0.28 16 / 14
0.0.27 16 / 14
0.0.26 16 / 14
0.0.25 16 / 14
0.0.24 16 / 14
0.0.23 16 / 14
0.0.22 16 / 14
0.0.21 16 / 14

v0.0.49

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.48

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: cpartee6 → coreymartin (on 2025-05-17, known maintainer) provenance

This version was published by a different npm account (coreymartin) than the most recent previously approved version (cpartee6) on 2025-05-17, but coreymartin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.0.47

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.46

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: coreymartin → cpartee6 (on 2025-05-17, known maintainer) provenance

This version was published by a different npm account (cpartee6) than the most recent previously approved version (coreymartin) on 2025-05-17, but cpartee6 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.0.45

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.44

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: cpartee6 → coreymartin (on 2025-05-15, known maintainer) provenance

This version was published by a different npm account (coreymartin) than the most recent previously approved version (cpartee6) on 2025-05-15, but coreymartin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.0.43

2 findings
MEDIUM Publisher changed: cpartee6 → ch-brian (on 2025-05-13, unremoved on npm for 431d) provenance

This version was published by a different npm account (ch-brian) than the most recent previously approved version (cpartee6) on 2025-05-13. It has since remained available on npm for 431 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.42

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.41

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.40

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.39

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.38

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.37

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.36

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.35

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.34

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.33

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.32

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.31

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.30

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.29

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.28

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.27

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.26

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.25

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.24

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.23

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.22

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.21

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.