@lit-protocol/misc-browser
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:depd | AI (phantom-deps): Monorepo shared config reference; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:siwe | AI (phantom-deps): Monorepo shared config reference; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:ethers | AI (phantom-deps): Monorepo shared config reference; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@openagenda/verror | AI (phantom-deps): Monorepo shared config reference; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@lit-protocol/types | AI (phantom-deps): Same-org monorepo dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@lit-protocol/contracts | AI (phantom-deps): Same-org monorepo dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@lit-protocol/accs-schemas | AI (phantom-deps): Same-org monorepo dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@ethersproject/abstract-provider | AI (phantom-deps): Monorepo shared config reference; stable false positive for this package. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 7.4.0 | 11 / 0 | |
| 7.3.1 | 11 / 0 | |
| 7.3.0 | 11 / 0 | |
| 7.2.1 | 11 / 0 | |
| 7.2.0 | 11 / 0 | |
| 7.1.3 | 11 / 0 | |
| 7.1.2 | 11 / 0 | |
| 7.1.1 | 11 / 0 | |
| 7.1.0 | 11 / 0 | |
| 7.0.9 | 11 / 0 | |
| 7.0.8 | 11 / 0 | |
| 7.0.7 | 11 / 0 | |
| 7.0.6 | 11 / 0 | |
| 7.0.5 | 11 / 0 | |
| 7.0.4 | 11 / 0 | |
| 7.0.3 | 11 / 0 | |
| 7.0.2 | 11 / 0 | |
| 7.0.1 | 11 / 0 | |
| 7.0.0 | 10 / 0 |
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
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 (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 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.