@web3auth/auth
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@toruslabs/tweetnacl-js | AI (dependencies): Torus Labs-namespaced tweetnacl fork; consistent with this package's dependency ecosystem across versions. | ai | |
| phantom-deps | phantom-dep:deepmerge | AI (phantom-deps): deepmerge is a declared runtime dep in package.json; phantom-dep false positive for this package. | ai | |
| dependencies | unvetted-dep:@toruslabs/ffjavascript | AI (dependencies): First-party Torus Labs dependency; same org as the package publisher. | ai | |
| dependencies | unvetted-dep:@toruslabs/secure-pub-sub | AI (dependencies): First-party Torus Labs dependency; same org as the package publisher. | ai | |
| dependencies | unvetted-dep:@toruslabs/constants | AI (dependencies): First-party Torus Labs dependency; same org as the package publisher. | ai | |
| dependencies | unvetted-dep:@toruslabs/metadata-helpers | AI (dependencies): First-party Torus Labs dependency; same org as the package publisher. | ai | |
| provenance | no-provenance | AI (provenance): Established Torus Labs package; absence of provenance is common and not a risk signal here. | ai | |
| dependencies | unvetted-dep:@toruslabs/session-manager | AI (dependencies): First-party Torus Labs dependency; same org as the package publisher. | ai | |
| dependencies | unvetted-dep:@toruslabs/customauth | AI (dependencies): First-party Torus Labs dependency; same org as the package publisher. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 11.8.1 | 14 / 25 | |
| 11.8.0 | 14 / 25 | |
| 11.7.0 | 14 / 25 | |
| 11.6.0 | 14 / 25 | |
| 11.4.3 | 14 / 25 | |
| 11.4.0 | 14 / 25 | |
| 11.3.0 | 14 / 25 | |
| 11.2.1 | 14 / 25 | |
| 11.1.1 | 16 / 24 | |
| 11.1.0 | 16 / 24 | |
| 10.8.0 | 23 / 27 | |
| 10.7.0 | 23 / 27 | |
| 10.6.0 | 23 / 27 |
v11.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.