rate-limit-redis
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Migrated to GitHub Actions CI/CD publishing with SLSA provenance; legitimate transition. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Major version bump after CI migration; dormancy pattern normal for this mature package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 6.0.0 | 0 / 26 | |
| 5.0.0 | 0 / 26 | |
| 4.3.1 | 0 / 26 | |
| 4.3.0 | 0 / 26 | |
| 4.2.3 | 0 / 26 | |
| 4.2.2 | 0 / 26 | |
| 4.2.1 | 0 / 26 | |
| 4.2.0 | 0 / 26 | |
| 4.1.2 | 0 / 26 | |
| 4.1.1 | 0 / 26 | |
| 4.1.0 | 0 / 26 | |
| 4.0.0 | 0 / 26 |
v6.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.