connect-redis
Redis session store for Connect
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Long-standing trusted maintainer (wavded) with 71 approved packages; missing gitHead is a publish-environment hygiene issue, not a security signal for this package. | ai | |
| provenance | no-provenance | AI (provenance): connect-redis is a well-established package; lack of Sigstore attestation is a hygiene concern, not a security risk given the publisher's track record. | ai |
Versions (showing 73 of 73)
| Version | Deps | Published |
|---|---|---|
| 9.0.0 | 0 / 10 | |
| 8.1.0 | 0 / 18 | |
| 8.0.3 | 0 / 18 | |
| 8.0.2 | 0 / 18 | |
| 8.0.1 | 0 / 19 | |
| 8.0.0 | 0 / 19 | |
| 7.1.1 | 0 / 16 | |
| 7.1.0 | 0 / 16 | |
| 7.0.1 | 0 / 16 | |
| 7.0.0 | 0 / 16 | |
| 6.1.3 | 0 / 10 | |
| 6.1.2 | 1 / 11 | |
| 6.1.1 | 0 / 10 | |
| 6.1.0 | 0 / 11 | |
| 6.0.0 | 0 / 9 | |
| 5.2.0 | 0 / 9 | |
| 5.1.0 | 0 / 9 | |
| 5.0.0 | 0 / 10 | |
| 4.0.4 | 0 / 10 | |
| 4.0.3 | 0 / 11 | |
| 4.0.2 | 0 / 11 | |
| 4.0.1 | 3 / 11 | |
| 4.0.0 | 0 / 11 | |
| 3.4.2 | 2 / 8 | |
| 3.4.1 | 2 / 8 | |
| 3.4.0 | 2 / 8 | |
| 3.3.3 | 2 / 8 | |
| 3.3.2 | 2 / 8 | |
| 3.3.1 | 2 / 8 | |
| 3.3.0 | 2 / 7 | |
| 3.2.0 | 2 / 7 | |
| 3.1.0 | 2 / 7 | |
| 3.0.2 | 2 / 7 | |
| 3.0.1 | 2 / 7 | |
| 3.0.0 | 2 / 7 | |
| 2.5.1 | 2 / 7 | |
| 2.5.0 | 2 / 7 | |
| 2.4.1 | 2 / 6 | |
| 2.4.0 | 2 / 6 | |
| 2.3.0 | 2 / 6 | |
| 2.2.0 | 2 / 6 | |
| 2.1.0 | 3 / 2 | |
| 2.0.0 | 2 / 1 | |
| 1.5.0 | 2 / 1 | |
| 1.4.7 | 2 / 1 | |
| 1.4.6 | 2 / 1 | |
| 1.4.5 | 2 / 1 | |
| 1.4.4 | 2 / 1 | |
| 1.4.3 | 2 / 1 | |
| 1.4.2 | 2 / 1 | |
| 1.4.1 | 2 / 1 | |
| 1.4.0 | 2 / 1 | |
| 1.3.0 | 2 / 1 | |
| 1.2.0 | 1 / 1 | |
| 1.1.0 | 1 / 1 | |
| 1.0.7 | 1 / 1 | |
| 1.0.6 | 1 / 1 | |
| 1.0.5 | 1 / 1 | |
| 1.0.4 | 1 / 0 | |
| 1.0.3 | 1 / 0 | |
| 1.0.2 | 1 / 0 | |
| 1.0.1 | 1 / 0 | |
| 1.0.0 | 1 / 0 | |
| 0.2.3 | 1 / 0 | |
| 0.2.2 | 1 / 0 | |
| 0.2.1 | 1 / 0 | |
| 0.2.0 | 0 / 0 | |
| 0.1.3 | 0 / 0 | |
| 0.1.2 | 0 / 0 | |
| 0.1.1 | 0 / 0 | |
| 0.1.0 | 0 / 0 | |
| 0.0.2 | 0 / 0 | |
| 0.0.1 | 0 / 0 |
v8.1.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: wavded.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.3
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: wavded.
v8.0.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: wavded.
v8.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.