@credenza3/core-web-evm-ext
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | encoded-string-file:dist/main.umd.cjs | AI (source-diff): Encoded strings are ethers.js unicode normalization tables bundled into dist; stable false positive for this package. | ai | |
| source-diff | encoded-string-file:dist/main.js | AI (source-diff): Same base64 unicode table pattern from ethers.js bundle; not a malicious payload. | ai | |
| phantom-deps | phantom-dep:siwe | AI (phantom-deps): siwe is a declared runtime dep bundled into dist; phantom-dep heuristic fires because it's not directly imported in source. | ai | |
| phantom-deps | phantom-dep:js-sha3 | AI (phantom-deps): js-sha3 is a declared runtime dep bundled into dist; same false-positive pattern as siwe. | ai |
v0.0.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.12
4 findingsThis version was published by a different npm account than previous versions on 2025-11-06. This could indicate a legitimate maintainer transition or an account compromise.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.