viem
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): viem has 3.5M weekly downloads and 2520 registry versions; the dormancy signal is a diff-baseline artifact, not real inactivity. SLSA provenance confirms legitimate CI/CD publishing. | ai | |
| dependencies | unvetted-dep:ox | AI (dependencies): ox is a well-known Ethereum primitives library from the same Wevm ecosystem as viem; its use is expected and appropriate. | ai | |
| source-diff | large-new-source-files | AI (source-diff): New files are Tempo chain feature additions (type definitions, action files) consistent with legitimate feature development in a major Ethereum library. | ai | |
| phantom-deps | phantom-dep:ws | AI (phantom-deps): ws is used for WebSocket RPC transport in viem; referenced in config/conditional imports, standard for this package. | ai | |
| provenance | publisher-changed | AI (provenance): Legitimate transition from personal npm account (jmoxey) to GitHub Actions CI/CD publishing with SLSA provenance attestation. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): 127.0.0.1:8545 is the standard Anvil/Hardhat local dev node address, hardcoded in the Anvil chain definition. Benign and expected for this library. | ai | |
| semgrep | semgrep:shady-links-tlds | AI (semgrep): viem ships hundreds of blockchain chain definitions with RPC URLs. TLD-based flagging is a systematic false positive for this package's core functionality. | ai | |
| typosquat | typosquat.levenshtein:vite | AI (typosquat): viem is a well-known Ethereum library, not a typosquat of vite. Coincidental Levenshtein proximity; entirely different domains and ecosystems. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 2.48.11 | 8 / 0 | |
| 2.48.8 | 8 / 0 | |
| 2.48.7 | 8 / 0 | |
| 2.48.6 | 8 / 0 | |
| 2.48.4 | 8 / 0 | |
| 2.47.5 | 8 / 0 | |
| 2.38.6 | 8 / 0 | |
| 2.38.5 | 8 / 0 | |
| 2.28.1 | 8 / 0 | |
| 2.21.58 | 9 / 0 |
v2.48.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.48.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.48.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.48.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.48.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.47.5
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-03-18. This could indicate a legitimate maintainer transition or an account compromise.
v2.38.6
2 findingsThis version was published by a different npm account than previous versions on 2025-11-01. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.38.5
2 findingsThis version was published by a different npm account than previous versions on 2025-10-28. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.28.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.21.58
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.