@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, so a manually published version cannot be tied back to a reviewed commit.
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 51 of 72)
| Version | Deps | Published |
|---|---|---|
| 3.1.47 | 2 / 23 | |
| 3.1.46 | 2 / 23 | |
| 3.1.45 | 2 / 23 | |
| 3.1.44 | 2 / 23 | |
| 3.1.43 | 2 / 23 | |
| 3.1.42 | 2 / 23 | |
| 3.1.41 | 2 / 23 | |
| 3.1.40 | 2 / 23 | |
| 3.1.36 | 2 / 23 | |
| 3.1.35 | 2 / 23 | |
| 3.1.34 | 2 / 23 | |
| 3.1.33 | 2 / 23 | |
| 3.1.32 | 2 / 23 | |
| 3.1.31 | 2 / 23 | |
| 3.1.30 | 2 / 23 | |
| 3.1.29 | 2 / 23 | |
| 3.1.28 | 2 / 23 | |
| 3.1.27 | 2 / 23 | |
| 3.1.26 | 2 / 23 | |
| 3.1.25 | 2 / 23 | |
| 3.1.24 | 2 / 23 | |
| 3.1.23 | 2 / 23 | |
| 3.1.22 | 2 / 23 | |
| 3.1.21 | 2 / 23 | |
| 3.1.20 | 2 / 23 | |
| 3.1.19 | 2 / 23 | |
| 3.1.18 | 2 / 23 | |
| 3.1.17 | 2 / 23 | |
| 3.1.16 | 2 / 23 | |
| 3.1.15 | 2 / 23 | |
| 3.1.14 | 2 / 23 | |
| 3.1.13 | 2 / 23 | |
| 3.1.12 | 2 / 23 | |
| 3.1.11 | 2 / 23 | |
| 3.1.10 | 2 / 23 | |
| 3.1.9 | 2 / 23 | |
| 3.1.8 | 2 / 23 | |
| 3.1.7 | 2 / 23 | |
| 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 |
v3.1.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.