@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 51 of 70)
| Version | Deps | Published |
|---|---|---|
| 1.45.0 | 4 / 1 | |
| 1.44.0 | 4 / 1 | |
| 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 | |
| 1.29.0 | 5 / 1 | |
| 1.28.1 | 5 / 1 | |
| 1.28.0 | 5 / 1 | |
| 1.27.1 | 5 / 1 | |
| 1.27.0 | 5 / 1 | |
| 1.26.0 | 5 / 1 | |
| 1.25.0 | 5 / 1 | |
| 1.24.0 | 5 / 1 | |
| 1.23.1 | 5 / 1 | |
| 1.23.0 | 5 / 1 | |
| 1.22.0 | 5 / 1 | |
| 1.21.0 | 5 / 1 | |
| 1.20.2 | 5 / 1 | |
| 1.20.1 | 5 / 1 | |
| 1.20.0 | 5 / 1 | |
| 1.19.0 | 5 / 1 | |
| 1.18.1 | 5 / 1 | |
| 1.18.0 | 5 / 1 | |
| 1.17.0 | 5 / 1 | |
| 1.16.0 | 6 / 1 | |
| 1.15.1 | 6 / 1 | |
| 1.15.0 | 6 / 1 | |
| 1.14.0 | 6 / 1 | |
| 1.13.0 | 6 / 1 | |
| 1.12.1 | 6 / 1 | |
| 1.12.0 | 6 / 1 | |
| 1.11.3 | 6 / 1 | |
| 1.11.2 | 6 / 1 | |
| 1.11.1 | 6 / 1 | |
| 1.11.0 | 6 / 1 | |
| 1.10.0 | 6 / 1 | |
| 1.9.2 | 6 / 1 | |
| 1.9.1 | 6 / 1 |
v1.45.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.44.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.29.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.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.18.1
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.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.