@lodestar/era
Era file handling module for 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 | publisher-changed | AI (provenance): Lodestar monorepo migrated from named maintainer to GitHub Actions CI publishing, confirmed by SLSA provenance attestation. This transition is a security improvement and generalizes to future versions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Mass-production signal reflects legitimate @lodestar/* monorepo package structure; no-keywords is trivial for a scoped ecosystem package. | ai | |
| typosquat | typosquat.levenshtein:koa | AI (typosquat): @lodestar/era is a scoped package in the well-known ChainSafe/lodestar Ethereum client ecosystem; levenshtein match to 'koa' is a false positive that will never be relevant. | ai | |
| phantom-deps | phantom-dep:uint8arraylist | AI (phantom-deps): uint8arraylist is a declared runtime dependency; phantom-dep flag indicates it may be used transitively or in config — not a security concern for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 1.43.0 | 7 / 0 | |
| 1.42.0 | 7 / 0 | |
| 1.41.1 | 7 / 0 | |
| 1.41.0 | 7 / 0 | |
| 1.40.0 | 7 / 0 | |
| 1.39.1 | 6 / 0 | |
| 1.39.0 | 6 / 0 | |
| 1.38.0 | 6 / 0 | |
| 1.37.0 | 6 / 0 | |
| 1.36.0 | 6 / 0 |
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.