@lit-protocol/auth-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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:ajv | AI (phantom-deps): Monorepo build artifact; declared in package.json but used transitively, stable false positive. | ai | |
| phantom-deps | phantom-dep:bech32 | AI (phantom-deps): Monorepo build artifact; declared in package.json but used transitively, stable false positive. | ai | |
| phantom-deps | phantom-dep:@openagenda/verror | AI (phantom-deps): Monorepo build artifact; declared in package.json but used transitively, stable false positive. | ai | |
| phantom-deps | phantom-dep:@lit-protocol/logger | AI (phantom-deps): Same-org sibling dep in monorepo; stable false positive. | ai | |
| phantom-deps | phantom-dep:@ethersproject/contracts | AI (phantom-deps): Monorepo build artifact; declared in package.json but used transitively, stable false positive. | ai | |
| phantom-deps | phantom-dep:@lit-protocol/accs-schemas | AI (phantom-deps): Same-org sibling dep in monorepo; stable false positive. | ai | |
| phantom-deps | phantom-dep:@ethersproject/abstract-provider | AI (phantom-deps): Monorepo build artifact; declared in package.json but used transitively, stable false positive. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 7.4.0 | 19 / 0 | |
| 7.3.1 | 19 / 0 | |
| 7.3.0 | 19 / 0 | |
| 7.2.1 | 19 / 0 | |
| 7.2.0 | 19 / 0 | |
| 7.1.3 | 19 / 0 | |
| 7.1.2 | 19 / 0 |
v7.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.