@signageos/redis
This library provides the Redis generic client wrapper and helper functions for signageOS projects.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/debug | AI (phantom-deps): @types/debug is declared in dependencies and used by runtime code; false positive. | ai | |
| phantom-deps | phantom-dep:@types/lodash | AI (phantom-deps): @types/lodash is declared in dependencies and used by runtime code; false positive. | ai | |
| typosquat | typosquat.levenshtein:redux | AI (typosquat): Scoped @signageos/redis wraps the redis client; Levenshtein match to 'redux' is a false positive. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 4.0.0 | 4 / 12 | |
| 3.3.0 | 6 / 13 | |
| 3.2.0 | 6 / 13 | |
| 3.1.2 | 6 / 13 | |
| 3.1.1 | 6 / 13 | |
| 3.1.0 | 7 / 13 | |
| 3.0.0 | 7 / 13 | |
| 2.2.0 | 7 / 13 | |
| 2.1.1 | 7 / 13 | |
| 2.1.0 | 7 / 13 | |
| 2.0.0 | 7 / 13 |
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.