@redis/time-series
This package provides support for the [RedisTimeSeries](https://redis.io/docs/data-types/timeseries/) module, which adds a time series data structure 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): Transition from leibale to dmaier-redislabs is a legitimate handoff within the Redis org; both are known node-redis maintainers. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Major version bump (1.x→5.x) with significant rewrite; new files are TypeScript declarations and command implementations. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Expected for a major version rewrite of the official @redis/time-series package; no suspicious content. | ai |
Versions (showing 23 of 23)
| 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.1.0 | 0 / 9 | |
| 1.0.5 | 0 / 9 | |
| 1.0.4 | 0 / 9 | |
| 1.0.3 | 0 / 9 |
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.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.