@lodestar/logger
Common NodeJS logger for Lodestar binaries
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Mass-production signal reflects the @lodestar/* monorepo structure; short README is typical for scoped utility packages in this project. Not indicative of spam or malice. | ai | |
| provenance | no-provenance | AI (provenance): Established ChainSafe/lodestar package with long track record; lack of Sigstore provenance is not a disqualifying signal here. | ai | |
| dependencies | unvetted-dep:@lodestar/utils | AI (dependencies): Sibling package in the same Lodestar monorepo (ChainSafe/lodestar); always co-released at matching versions. Not an independent supply chain risk. | ai | |
| dependencies | unvetted-dep:winston-daily-rotate-file | AI (dependencies): Well-known Winston transport plugin for log rotation; expected dependency for a logging package. No security concerns. | ai |
Versions (showing 51 of 54)
| Version | Deps | Published |
|---|---|---|
| 1.45.0 | 5 / 4 | |
| 1.44.0 | 5 / 4 | |
| 1.43.0 | 5 / 4 | |
| 1.42.0 | 5 / 4 | |
| 1.41.1 | 5 / 4 | |
| 1.41.0 | 5 / 4 | |
| 1.40.0 | 5 / 4 | |
| 1.39.1 | 5 / 4 | |
| 1.39.0 | 5 / 4 | |
| 1.38.0 | 4 / 4 | |
| 1.37.0 | 4 / 4 | |
| 1.36.0 | 4 / 4 | |
| 1.35.0 | 4 / 4 | |
| 1.34.1 | 4 / 4 | |
| 1.34.0 | 4 / 4 | |
| 1.33.0 | 4 / 4 | |
| 1.32.0 | 4 / 4 | |
| 1.31.0 | 4 / 4 | |
| 1.30.0 | 4 / 4 | |
| 1.29.0 | 4 / 4 | |
| 1.28.1 | 4 / 4 | |
| 1.28.0 | 4 / 4 | |
| 1.27.1 | 4 / 4 | |
| 1.27.0 | 4 / 4 | |
| 1.26.0 | 4 / 4 | |
| 1.25.0 | 4 / 4 | |
| 1.24.0 | 4 / 4 | |
| 1.23.1 | 4 / 4 | |
| 1.23.0 | 4 / 4 | |
| 1.22.0 | 4 / 4 | |
| 1.21.0 | 4 / 4 | |
| 1.20.2 | 4 / 4 | |
| 1.20.1 | 4 / 4 | |
| 1.20.0 | 4 / 4 | |
| 1.19.0 | 4 / 4 | |
| 1.18.1 | 4 / 4 | |
| 1.18.0 | 4 / 4 | |
| 1.17.0 | 4 / 4 | |
| 1.16.0 | 4 / 5 | |
| 1.15.1 | 4 / 5 | |
| 1.15.0 | 4 / 5 | |
| 1.14.0 | 4 / 5 | |
| 1.13.0 | 4 / 4 | |
| 1.12.1 | 4 / 4 | |
| 1.12.0 | 4 / 4 | |
| 1.11.3 | 4 / 4 | |
| 1.11.2 | 4 / 4 | |
| 1.11.1 | 4 / 4 | |
| 1.11.0 | 4 / 4 | |
| 1.10.0 | 4 / 3 | |
| 1.9.2 | 4 / 3 |
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. Consider requesting the maintainer enable provenance via CI/CD.
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.