redis-semaphore
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
Keywords
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 5.7.0 | 1 / 29 | |
| 5.6.2 | 1 / 29 | |
| 5.6.1 | 1 / 30 | |
| 5.6.0 | 1 / 30 | |
| 5.5.1 | 1 / 26 | |
| 5.5.0 | 1 / 26 | |
| 5.4.0 | 1 / 26 | |
| 5.3.1 | 1 / 26 | |
| 5.3.0 | 1 / 26 | |
| 5.2.0 | 2 / 27 | |
| 5.1.0 | 2 / 27 | |
| 5.0.0 | 2 / 27 |
v5.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.