@lodestar/validator
A Typescript implementation of the validator 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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher changed to GitHub Actions CI/CD with SLSA provenance attestation — this is a deliberate, security-improving migration for the ChainSafe/lodestar monorepo. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Lodestar is an active Ethereum consensus client with 2669 versions and 4.9k weekly downloads; SLSA attestation confirms legitimate CI/CD publishing. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): The flagged IP is 127.0.0.1 (localhost), used as a default local RPC endpoint config. This is standard practice for Ethereum client tooling and not a malicious remote connection. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 1.43.0 | 10 / 5 | |
| 1.42.0 | 10 / 5 | |
| 1.41.1 | 10 / 5 | |
| 1.41.0 | 10 / 5 | |
| 1.40.0 | 10 / 5 | |
| 1.39.1 | 10 / 5 | |
| 1.39.0 | 10 / 5 | |
| 1.38.0 | 10 / 3 | |
| 1.37.0 | 10 / 3 | |
| 1.36.0 | 10 / 3 | |
| 1.35.0 | 10 / 3 | |
| 1.34.1 | 10 / 3 | |
| 1.34.0 | 10 / 3 | |
| 1.33.0 | 10 / 3 | |
| 1.32.0 | 10 / 3 | |
| 1.31.0 | 10 / 3 | |
| 1.30.0 | 10 / 3 |
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.41.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-19. 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.
v1.40.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-11. 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.
v1.39.1
2 findingsThis version was published by a different npm account than previous versions on 2026-01-30. 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.
v1.39.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-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.
v1.38.0
2 findingsThis version was published by a different npm account than previous versions on 2025-12-15. 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.
v1.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.34.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.32.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.
v1.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.