@lodestar/prover
A Typescript implementation of the Ethereum Consensus light client
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:http-proxy | AI (dependencies): http-proxy is a well-known library; its use is expected in a prover/proxy tool that mediates Ethereum JSON-RPC traffic. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding is a core operation in Ethereum tooling; this is a standard hex-string-to-buffer utility with no malicious payload. Stable false positive for this package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.43.0 | 22 / 8 | |
| 1.42.0 | 22 / 8 | |
| 1.41.1 | 22 / 8 | |
| 1.40.0 | 22 / 8 | |
| 1.39.1 | 22 / 8 | |
| 1.39.0 | 22 / 8 | |
| 1.37.0 | 21 / 6 | |
| 1.36.0 | 21 / 6 | |
| 1.31.0 | 21 / 6 |
v1.43.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.42.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.41.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.40.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.39.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.39.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.36.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.