@diia-inhouse/redis
Redis services - redlock, pubsub, cache and store
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:redis-semaphore | AI (dependencies): redis-semaphore is a well-known legitimate npm package for distributed Redis locking; a natural and expected dependency for a Redis utility library. | ai | |
| typosquat | typosquat.levenshtein:redux | AI (typosquat): False positive: '@diia-inhouse/redis' is a Redis client wrapper in a scoped namespace, not a typosquat of the Redux state management library. Completely different domain and purpose. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 3.1.6 | 2 / 23 | |
| 3.1.5 | 2 / 23 | |
| 3.1.4 | 2 / 23 | |
| 3.1.3 | 2 / 23 | |
| 3.1.2 | 2 / 23 | |
| 3.1.1 | 2 / 23 | |
| 3.1.0 | 2 / 23 | |
| 2.30.21 | 2 / 21 | |
| 2.30.16 | 2 / 21 | |
| 2.30.15 | 2 / 21 | |
| 2.30.14 | 2 / 21 | |
| 2.30.13 | 2 / 21 | |
| 2.30.12 | 2 / 21 | |
| 2.30.11 | 2 / 21 | |
| 2.30.10 | 2 / 21 | |
| 2.30.9 | 2 / 21 | |
| 2.30.8 | 2 / 21 | |
| 2.30.7 | 2 / 21 | |
| 2.30.6 | 2 / 21 | |
| 2.30.5 | 2 / 21 | |
| 2.30.4 | 2 / 21 | |
| 2.30.3 | 2 / 21 | |
| 2.30.2 | 2 / 21 | |
| 2.30.1 | 2 / 21 | |
| 2.30.0 | 2 / 21 | |
| 2.29.3 | 2 / 21 | |
| 2.29.2 | 2 / 21 | |
| 2.29.1 | 2 / 21 | |
| 2.29.0 | 2 / 21 | |
| 2.28.0 | 2 / 21 |
v3.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.30.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.30.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.30.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.30.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.30.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.30.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.30.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.30.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.29.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.29.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.29.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.