← Home

@lit-protocol/misc

19
Versions
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

glitch003adarsh-kumar28websaamhwrdtmfamuramaximushaximusspacesailorawisniew

Keywords

library

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:hex-decode AI (semgrep): Hex conversion is standard EC point decompression math (y-coordinate), not obfuscated payload handling. ai
phantom-deps phantom-dep:depd AI (phantom-deps): depd is a declared transitive/peer dep; phantom-dep heuristic false positive for this package. ai
phantom-deps phantom-dep:siwe AI (phantom-deps): siwe is a declared dep used indirectly; stable false positive for this package. ai
phantom-deps phantom-dep:util AI (phantom-deps): util is a declared dep; phantom-dep heuristic false positive for this package. ai
phantom-deps phantom-dep:@openagenda/verror AI (phantom-deps): Declared dep used indirectly; stable false positive for this package. ai
phantom-deps phantom-dep:@lit-protocol/contracts AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic false positive. ai
phantom-deps phantom-dep:@lit-protocol/accs-schemas AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic false positive. ai
phantom-deps phantom-dep:@ethersproject/abstract-provider AI (phantom-deps): Declared dep used indirectly via ethers; stable false positive for this package. ai

Versions (showing 19 of 19)

Version Deps Published
7.4.0 16 / 0
7.3.1 16 / 0
7.3.0 16 / 0
7.2.1 16 / 0
7.2.0 16 / 0
7.1.3 16 / 0
7.1.2 16 / 0
7.1.1 16 / 0
7.1.0 16 / 0
7.0.9 16 / 0
7.0.8 16 / 0
7.0.7 16 / 0
7.0.6 16 / 0
7.0.5 16 / 0
7.0.4 16 / 0
7.0.3 16 / 0
7.0.2 16 / 0
7.0.1 16 / 0
7.0.0 15 / 0

v7.1.1

1 finding
LOW No provenance attestation provenance

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

v7.1.0

1 finding
LOW No provenance attestation provenance

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

v7.0.9

1 finding
LOW No provenance attestation provenance

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

v7.0.8

1 finding
LOW No provenance attestation provenance

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

v7.0.7

1 finding
LOW No provenance attestation provenance

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

v7.0.6

1 finding
LOW No provenance attestation provenance

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

v7.0.5

1 finding
LOW No provenance attestation provenance

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

v7.0.4

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: famura → websaam (on 2025-01-02, known maintainer) provenance

This version was published by a different npm account (websaam) than the most recent previously approved version (famura) on 2025-01-02, but websaam 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.3

1 finding
LOW No provenance attestation provenance

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

v7.0.2

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: websaam → famura (on 2024-12-09, known maintainer) provenance

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 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.

v7.0.0

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.