@redis/client
The source code and documentation for this package are in the main [node-redis](https://github.com/redis/node-redis) repo.
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 | publisher-changed | AI (provenance): Legitimate maintainer transition within the Redis org; dmaier-redislabs is a Redis Labs employee with strong track record (167 approved versions). | ai |
Versions (showing 48 of 48)
| Version | Deps | Published |
|---|---|---|
| 6.0.0 | 1 / 6 | |
| 5.12.1 | 1 / 6 | |
| 5.12.0 | 1 / 6 | |
| 5.11.0 | 1 / 4 | |
| 5.10.0 | 1 / 3 | |
| 5.9.0 | 1 / 3 | |
| 5.8.3 | 1 / 3 | |
| 5.8.2 | 1 / 3 | |
| 5.8.1 | 1 / 3 | |
| 5.8.0 | 1 / 3 | |
| 5.7.0 | 1 / 3 | |
| 5.6.1 | 1 / 3 | |
| 5.6.0 | 1 / 3 | |
| 5.5.6 | 1 / 3 | |
| 5.5.5 | 1 / 3 | |
| 5.1.1 | 1 / 3 | |
| 5.1.0 | 1 / 3 | |
| 5.0.1 | 1 / 3 | |
| 5.0.0 | 1 / 3 | |
| 1.6.1 | 3 / 15 | |
| 1.6.0 | 3 / 15 | |
| 1.5.17 | 3 / 15 | |
| 1.5.16 | 3 / 15 | |
| 1.5.15 | 3 / 15 | |
| 1.5.14 | 3 / 15 | |
| 1.5.13 | 3 / 15 | |
| 1.5.12 | 3 / 15 | |
| 1.5.11 | 3 / 15 | |
| 1.5.10 | 3 / 15 | |
| 1.5.9 | 3 / 15 | |
| 1.5.8 | 3 / 15 | |
| 1.5.7 | 3 / 15 | |
| 1.5.6 | 3 / 15 | |
| 1.5.5 | 3 / 15 | |
| 1.5.4 | 3 / 15 | |
| 1.5.3 | 3 / 15 | |
| 1.5.2 | 3 / 15 | |
| 1.5.1 | 3 / 15 | |
| 1.5.0 | 3 / 15 | |
| 1.4.2 | 3 / 15 | |
| 1.4.1 | 3 / 15 | |
| 1.4.0 | 3 / 15 | |
| 1.3.1 | 3 / 15 | |
| 1.3.0 | 3 / 15 | |
| 1.2.0 | 3 / 15 | |
| 1.1.1 | 3 / 15 | |
| 1.1.0 | 3 / 15 | |
| 1.0.6 | 3 / 15 |
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
2 findingsThis version was published by a different npm account than previous versions on 2025-04-30. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.