@lodestar/reqresp
A Typescript implementation of the Ethereum Consensus Req/Resp protocol
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): ChainSafe/lodestar transitioned to GitHub Actions CI publishing with SLSA provenance attestation — a security improvement, not a takeover signal. Stable for this package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy is explained by the transition to GitHub Actions publishing with SLSA attestation from the official ChainSafe/lodestar repo. Not indicative of account takeover. | ai | |
| phantom-deps | phantom-dep:it-all | AI (phantom-deps): it-all is a legitimate libp2p ecosystem package; phantom-dep finding is a false positive common in monorepo/config-driven setups. | ai | |
| typosquat | typosquat.levenshtein:request | AI (typosquat): @lodestar/reqresp is named after 'request/response' in the Ethereum P2P protocol context, not a typosquat of the 'request' npm package. This is a stable false positive for this package. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 1.43.0 | 10 / 7 | |
| 1.42.0 | 10 / 7 | |
| 1.41.1 | 10 / 7 | |
| 1.41.0 | 10 / 7 | |
| 1.40.0 | 11 / 8 | |
| 1.39.1 | 11 / 8 | |
| 1.39.0 | 11 / 8 | |
| 1.38.0 | 11 / 3 | |
| 1.37.0 | 11 / 3 | |
| 1.36.0 | 11 / 3 | |
| 1.35.0 | 11 / 3 | |
| 1.34.1 | 11 / 3 | |
| 1.34.0 | 11 / 3 | |
| 1.33.0 | 11 / 3 | |
| 1.32.0 | 11 / 3 | |
| 1.31.0 | 11 / 3 | |
| 1.30.0 | 11 / 3 |
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.
v1.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.34.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.