@lit-protocol/core
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@lit-protocol/accs-schemas | AI (phantom-deps): Same-org config reference, not imported directly; stable false positive. | ai | |
| phantom-deps | phantom-dep:@ethersproject/abstract-provider | AI (phantom-deps): Config-file reference only; stable false positive. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is a same-org sibling package, expected in monorepo release. | ai | |
| phantom-deps | phantom-dep:jose | AI (phantom-deps): Same monorepo pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:pako | AI (phantom-deps): Same monorepo pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:siwe | AI (phantom-deps): Same monorepo pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:util | AI (phantom-deps): Same monorepo pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:bech32 | AI (phantom-deps): Same monorepo pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:process | AI (phantom-deps): Same monorepo pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:multiformats | AI (phantom-deps): Same monorepo pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:date-and-time | AI (phantom-deps): Same monorepo pattern; stable false positive. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped @lit-protocol/core is part of the established Lit Protocol SDK; levenshtein match against 'cors' is coincidental. | ai | |
| phantom-deps | phantom-dep:@lit-protocol/nacl | AI (phantom-deps): Same-scope sibling dep in monorepo; stable false positive. | ai | |
| phantom-deps | phantom-dep:@lit-protocol/wasm | AI (phantom-deps): Same-scope sibling dep in monorepo; stable false positive. | ai | |
| phantom-deps | phantom-dep:@openagenda/verror | AI (phantom-deps): Same monorepo pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@lit-protocol/logger | AI (phantom-deps): Same-scope sibling dep in monorepo; stable false positive. | ai | |
| phantom-deps | phantom-dep:@lit-protocol/contracts | AI (phantom-deps): Same-scope sibling dep in monorepo; stable false positive. | ai | |
| phantom-deps | phantom-dep:@ethersproject/contracts | AI (phantom-deps): Same monorepo pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@ethersproject/providers | AI (phantom-deps): Same monorepo pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@lit-protocol/uint8arrays | AI (phantom-deps): Same-scope sibling dep in monorepo; stable false positive. | ai | |
| phantom-deps | phantom-dep:@ethersproject/abi | AI (phantom-deps): Same monorepo pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:ajv | AI (phantom-deps): Monorepo build artifact; declared deps used transitively or in config files, stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:depd | AI (phantom-deps): Same monorepo pattern; stable false positive. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 7.4.0 | 30 / 0 | |
| 7.3.1 | 30 / 0 | |
| 7.3.0 | 30 / 0 | |
| 7.2.3 | 24 / 0 | |
| 7.2.1 | 30 / 0 | |
| 7.2.0 | 30 / 0 | |
| 7.1.3 | 30 / 0 | |
| 7.1.2 | 30 / 0 | |
| 7.0.6 | 29 / 0 | |
| 7.0.4 | 29 / 0 | |
| 7.0.2 | 29 / 0 | |
| 7.0.1 | 29 / 0 | |
| 7.0.0 | 28 / 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.0.6
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.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.