@redis/bloom
This package provides support for the [RedisBloom](https://redis.io/docs/data-types/probabilistic/) module, which adds additional probabilistic data structures to Redis.
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): dmaier-redislabs is a Redis Labs employee with strong track record (167 approved packages); this is a legitimate internal maintainer transition within the Redis org. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers dmaier-redislabs and shaya-redis are Redis Labs employees; consistent with legitimate org-level maintainer management. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 6.0.0 | 0 / 1 | |
| 5.12.1 | 0 / 1 | |
| 5.12.0 | 0 / 1 | |
| 5.11.0 | 0 / 1 | |
| 5.10.0 | 0 / 1 | |
| 5.9.0 | 0 / 1 | |
| 5.8.3 | 0 / 1 | |
| 5.8.2 | 0 / 1 | |
| 5.8.1 | 0 / 1 | |
| 5.8.0 | 0 / 1 | |
| 5.7.0 | 0 / 1 | |
| 5.6.1 | 0 / 1 | |
| 5.6.0 | 0 / 1 | |
| 5.5.6 | 0 / 1 | |
| 5.5.5 | 0 / 1 | |
| 5.1.1 | 0 / 1 | |
| 5.1.0 | 0 / 1 | |
| 5.0.1 | 0 / 1 | |
| 5.0.0 | 0 / 1 | |
| 1.2.0 | 0 / 9 | |
| 1.1.0 | 0 / 9 | |
| 1.0.2 | 0 / 9 | |
| 5.9.0-beta.3 | 0 / 1 | |
| 5.9.0-beta.2 | 0 / 1 | |
| 5.9.0-beta.1 | 0 / 1 | |
| 5.9.0-beta.0 | 0 / 1 |
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.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.