@lit-protocol/contracts-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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Known org maintainer rotation, confirmed by provenance INFO match on prior approved versions. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Normal maintainer turnover within same trusted org, no takeover indicators. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): No material diff vs last approved version; benign gap in publishing cadence. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is same-org @lit-protocol/contracts sibling package. | ai | |
| phantom-deps | phantom-dep:siwe | AI (phantom-deps): Sign-In with Ethereum dep; used indirectly; stable false positive. | ai | |
| phantom-deps | phantom-dep:util | AI (phantom-deps): Node.js util polyfill; stable false positive. | ai | |
| phantom-deps | phantom-dep:bech32 | AI (phantom-deps): Address encoding dep; stable false positive. | ai | |
| phantom-deps | phantom-dep:process | AI (phantom-deps): Node.js process polyfill; stable false positive. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Standard JWT body parsing; not obfuscation or payload hiding. | ai | |
| phantom-deps | phantom-dep:@lit-protocol/contracts | AI (phantom-deps): Same org scope; stable false positive. | ai | |
| phantom-deps | phantom-dep:@ethersproject/contracts | AI (phantom-deps): Ethers dep; stable false positive. | ai | |
| phantom-deps | phantom-dep:@lit-protocol/accs-schemas | AI (phantom-deps): Same org scope; stable false positive. | ai | |
| phantom-deps | phantom-dep:@ethersproject/abstract-provider | AI (phantom-deps): Ethers dep; stable false positive. | ai | |
| phantom-deps | phantom-dep:@openagenda/verror | AI (phantom-deps): Error utility dep; stable false positive. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decode used for pubkey-to-ETH-address conversion; legitimate crypto operation. | ai | |
| phantom-deps | phantom-dep:ajv | AI (phantom-deps): Config/schema validation dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:depd | AI (phantom-deps): Transitive utility dep; stable false positive. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 7.4.0 | 20 / 0 | |
| 7.3.1 | 20 / 0 | |
| 7.3.0 | 20 / 0 | |
| 7.2.3 | 14 / 0 | |
| 7.2.1 | 20 / 0 | |
| 7.2.0 | 20 / 0 | |
| 7.1.3 | 20 / 0 | |
| 7.1.2 | 20 / 0 | |
| 7.1.1 | 20 / 0 | |
| 7.1.0 | 20 / 0 | |
| 7.0.9 | 20 / 0 | |
| 7.0.8 | 20 / 0 | |
| 7.0.7 | 20 / 0 | |
| 7.0.6 | 20 / 0 | |
| 7.0.5 | 20 / 0 | |
| 7.0.4 | 20 / 0 | |
| 7.0.3 | 20 / 0 | |
| 7.0.2 | 20 / 0 | |
| 7.0.1 | 20 / 0 | |
| 7.0.0 | 19 / 0 |
v7.2.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (glitch003) than the most recent previously approved version (websaam) on 2025-08-05, but glitch003 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.
v7.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (famura) than the most recent previously approved version (websaam) on 2024-12-23, but famura 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.
v7.0.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (famura) than the most recent previously approved version (websaam) on 2024-12-09, but famura 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.
v7.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.