@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 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 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 |
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
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.40.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.39.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.39.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.38.0
1 findingPublished 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.35.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.