@lodestar/spec-test-util
Spec test suite generator from yaml test files
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): Part of the well-established ChainSafe/lodestar monorepo with 2679 versions and 1390 days of history. Mass-production signal reflects monorepo publishing pattern, not spam. | ai | |
| provenance | no-provenance | AI (provenance): Established ChainSafe Systems package with trusted publisher history; lack of provenance attestation is not a concern for this package. | ai | |
| provenance | slsa-provenance | AI (provenance): ChainSafe/lodestar publishes via CI/CD with SLSA provenance; this is a stable, expected signal for this package. | ai |
Versions (showing 51 of 71)
| Version | Deps | Published |
|---|---|---|
| 1.45.0 | 4 / 0 | |
| 1.44.0 | 4 / 0 | |
| 1.43.0 | 4 / 0 | |
| 1.42.0 | 4 / 0 | |
| 1.41.1 | 4 / 0 | |
| 1.41.0 | 4 / 0 | |
| 1.40.0 | 4 / 0 | |
| 1.39.1 | 4 / 0 | |
| 1.39.0 | 4 / 0 | |
| 1.38.0 | 4 / 0 | |
| 1.37.0 | 4 / 0 | |
| 1.36.0 | 4 / 0 | |
| 1.35.0 | 4 / 0 | |
| 1.34.1 | 4 / 0 | |
| 1.34.0 | 4 / 0 | |
| 1.33.0 | 4 / 0 | |
| 1.32.0 | 4 / 0 | |
| 1.31.0 | 4 / 0 | |
| 1.30.0 | 6 / 1 | |
| 1.29.0 | 6 / 1 | |
| 1.28.1 | 6 / 1 | |
| 1.28.0 | 6 / 1 | |
| 1.27.1 | 6 / 1 | |
| 1.27.0 | 6 / 1 | |
| 1.26.0 | 6 / 1 | |
| 1.25.0 | 6 / 1 | |
| 1.24.0 | 6 / 1 | |
| 1.23.1 | 6 / 1 | |
| 1.23.0 | 6 / 1 | |
| 1.22.0 | 6 / 1 | |
| 1.21.0 | 6 / 1 | |
| 1.20.2 | 6 / 1 | |
| 1.20.1 | 6 / 1 | |
| 1.20.0 | 6 / 1 | |
| 1.19.0 | 6 / 1 | |
| 1.18.1 | 6 / 1 | |
| 1.18.0 | 6 / 1 | |
| 1.17.0 | 6 / 1 | |
| 1.16.0 | 6 / 1 | |
| 1.15.1 | 7 / 2 | |
| 1.15.0 | 7 / 2 | |
| 1.14.0 | 8 / 2 | |
| 1.13.0 | 8 / 2 | |
| 1.12.1 | 8 / 2 | |
| 1.12.0 | 8 / 2 | |
| 1.11.3 | 8 / 2 | |
| 1.11.2 | 8 / 2 | |
| 1.11.1 | 8 / 2 | |
| 1.11.0 | 8 / 2 | |
| 1.10.0 | 8 / 2 | |
| 1.9.2 | 8 / 2 |
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.