@web3auth/core
1
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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
shubhamtoruschaitanyapotti
Keywords
web3Auth/coreweb3AuthmultichainWalletblockchainethereumsolana
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Legitimate scoped Web3Auth package; not a typosquat of cors — different namespace and purpose entirely. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 4.6.0 | 4 / 0 |
v4.6.0
2 findings
HIGH
typosquat.levenshtein: Possible typosquat of 'cors'
typosquat
Package name '@web3auth/core' is 1 edit(s) away from popular package 'cors'.
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.