@signinwithethereum/siwe
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/ethersCompat-Df4a6QIZ.js | AI (source-diff): Minified rolldown/vite build artifact (ESM variant) containing EIP-6492 signature validation code. Standard build output for this SIWE library, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/ethersCompat-CxsR3viR.cjs | AI (source-diff): Minified rolldown/vite build artifact containing EIP-6492 signature validation bytecode and ethers compatibility shims. Standard build output for this SIWE library, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/utils-DEHhwve8.cjs | AI (source-diff): Minified rolldown/vite build artifact containing SIWE error enums and utility code. Content is clearly legitimate library internals, not malicious obfuscation. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common for many legitimate packages; not a disqualifying signal for this package given all other context is clean. | ai | |
| source-diff | obfuscated-file:dist/ethersCompat-DyVMp-tf.cjs | AI (source-diff): Long-line content is minified EVM bytecode (EIP-6492 validator) embedded in a build artifact — expected for a SIWE/Ethereum library, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/ethersCompat-CAvhV6Kp.js | AI (source-diff): Same as CJS counterpart: minified EIP-6492 bytecode in a bundler output file. Standard pattern for Ethereum libraries, not malicious obfuscation. | ai | |
| typosquat | typosquat.levenshtein:vite | AI (typosquat): Scoped package @signinwithethereum/siwe is the official Sign-In-With-Ethereum library; 'siwe' vs 'vite' Levenshtein match is a false positive with no impersonation intent. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 4.2.0 | 1 / 3 | |
| 4.1.0 | 1 / 3 | |
| 4.0.3 | 1 / 3 | |
| 4.0.2 | 1 / 3 | |
| 4.0.1 | 1 / 3 | |
| 4.0.0 | 1 / 3 |
v4.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.