@lodestar/api
A Typescript REST client for the Ethereum Consensus API
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): ChainSafe/lodestar migrated publishing from personal account 'wemeetagain' to GitHub Actions CI/CD with SLSA provenance. This is a legitimate, security-improving workflow change that generalizes to all future versions. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Apparent dormancy is an artifact of the publisher account change, not actual inactivity. Package has 2674 versions and is actively maintained by ChainSafe Systems. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @lodestar/api has no relation to 'joi'. Levenshtein match is a false positive for this well-known Ethereum project. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped package @lodestar/api has no relation to 'ajv'. Levenshtein match is a false positive for this well-known Ethereum project. | ai | |
| dependencies | unvetted-dep:@chainsafe/ssz | AI (dependencies): @chainsafe/ssz is a first-party ChainSafe dependency used across the Lodestar monorepo for Ethereum SSZ serialization. Expected and stable. | ai | |
| typosquat | typosquat.levenshtein:hapi | AI (typosquat): @lodestar/api is a scoped package from ChainSafe Systems (Lodestar Ethereum client). Levenshtein match to 'hapi' is a false positive — no impersonation intent. | ai | |
| dependencies | unvetted-dep:@lodestar/utils | AI (dependencies): @lodestar/utils is an internal monorepo sibling package. Expected dependency for this package. | ai | |
| dependencies | unvetted-dep:@lodestar/config | AI (dependencies): @lodestar/config is an internal monorepo sibling package. Expected dependency for this package. | ai | |
| dependencies | unvetted-dep:@chainsafe/persistent-merkle-tree | AI (dependencies): @chainsafe/persistent-merkle-tree is a first-party ChainSafe dependency for Ethereum Merkle tree operations. Expected and stable. | ai | |
| dependencies | unvetted-dep:@lodestar/types | AI (dependencies): @lodestar/types is an internal monorepo sibling package. Expected dependency for this package. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package @lodestar/api has no relation to 'pg'. Levenshtein match is a false positive for this well-known Ethereum project. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 1.43.0 | 8 / 4 | |
| 1.42.0 | 8 / 4 | |
| 1.41.1 | 8 / 4 | |
| 1.41.0 | 8 / 4 | |
| 1.40.0 | 8 / 4 | |
| 1.39.1 | 8 / 4 | |
| 1.39.0 | 8 / 4 | |
| 1.38.0 | 8 / 4 | |
| 1.37.0 | 8 / 4 | |
| 1.36.0 | 8 / 4 | |
| 1.35.0 | 8 / 4 | |
| 1.34.1 | 8 / 4 | |
| 1.34.0 | 8 / 4 | |
| 1.33.0 | 8 / 4 | |
| 1.32.0 | 8 / 4 | |
| 1.31.0 | 8 / 4 | |
| 1.30.0 | 8 / 4 |
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
2 findingsPackage name '@lodestar/api' is 1 edit(s) away from popular package 'hapi'.
Published 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. Consider requesting the maintainer enable provenance via CI/CD.
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.