@lodestar/db
DB modules of Lodestar
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established ChainSafe/lodestar monorepo package; lack of provenance is consistent across all versions and not a security concern here. | ai | |
| provenance | publisher-changed | AI (provenance): ChainSafe/lodestar migrated to GitHub Actions CI publishing with SLSA provenance attestation. This publisher change is a legitimate CI/CD transition, not a takeover. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy is explained by the migration from manual to GitHub Actions publishing. Package has 2674 versions and active download history; not a takeover scenario. | ai | |
| phantom-deps | phantom-dep:it-all | AI (phantom-deps): it-all is a declared runtime dependency in a monorepo package; phantom-dep detection is a known false positive in this context. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): @lodestar/db is a scoped package in the Lodestar Ethereum client monorepo; levenshtein similarity to 'pg' is purely coincidental and not a typosquat. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): @lodestar/db is a scoped package in the Lodestar Ethereum client monorepo; levenshtein similarity to 'qs' is purely coincidental and not a typosquat. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 1.43.0 | 4 / 1 | |
| 1.42.0 | 4 / 1 | |
| 1.41.1 | 4 / 1 | |
| 1.41.0 | 4 / 1 | |
| 1.40.0 | 5 / 1 | |
| 1.39.1 | 5 / 1 | |
| 1.39.0 | 5 / 1 | |
| 1.38.0 | 5 / 1 | |
| 1.37.0 | 5 / 1 | |
| 1.36.0 | 6 / 1 | |
| 1.34.1 | 5 / 1 | |
| 1.34.0 | 5 / 1 | |
| 1.33.0 | 5 / 1 | |
| 1.32.0 | 5 / 1 | |
| 1.31.0 | 5 / 1 | |
| 1.30.0 | 5 / 1 |
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. 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.34.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.34.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.33.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.32.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.