redis-commands
Redis commands
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 |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is used to load internal plugin modules by path in a controlled loop — a standard extension pattern for this Redis commands library, not a security risk. | ai | |
| provenance | no-provenance | AI (provenance): Established package with 2.3M weekly downloads and trusted publisher; lack of Sigstore provenance is common and not a risk signal here. | ai | |
| source-diff | obfuscated-file:coverage/lcov-report/prettify.js | AI (source-diff): This is Google's prettify.js from Istanbul's lcov-report output — standard coverage artifact, not obfuscated malicious code. | ai | |
| maintainer-change | maintainer-takeover | AI (maintainer-change): Legitimate transfer to luin (ioredis author) under NodeRedis org in 2015; well-established maintainer with 37 approved packages. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Original maintainer replaced by luin as part of legitimate project transfer to NodeRedis org. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from yuanchuan to luin was a legitimate project transfer in 2015 to the ioredis maintainer. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): luin is the ioredis author and legitimate new maintainer of this NodeRedis org package. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 1.7.0 | 0 / 8 | |
| 1.6.0 | 0 / 8 | |
| 1.5.0 | 0 / 8 | |
| 1.4.0 | 0 / 8 | |
| 1.3.5 | 0 / 8 | |
| 1.3.4 | 0 / 8 | |
| 1.3.3 | 0 / 8 | |
| 1.3.2 | 0 / 8 | |
| 1.3.1 | 0 / 8 | |
| 1.3.0 | 0 / 8 | |
| 1.2.0 | 0 / 6 | |
| 1.1.0 | 0 / 4 | |
| 1.0.2 | 0 / 4 | |
| 1.0.1 | 0 / 4 | |
| 1.0.0 | 0 / 4 | |
| 0.0.3 | 1 / 2 | |
| 0.0.2 | 1 / 2 | |
| 0.0.1 | 1 / 2 |
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-07-25. This could indicate a legitimate maintainer transition or an account compromise.
v1.5.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-05-10. This could indicate a legitimate maintainer transition or an account compromise.
v1.4.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-10-08. This could indicate a legitimate maintainer transition or an account compromise.
v1.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
3 findingsAll previous maintainers (yuanchuan) were replaced by new maintainers (bridgear, luin). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2015-11-23. 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.0.0
3 findingsAll previous maintainers (yuanchuan) were replaced by new maintainers (luin). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2015-10-31. 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.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.