@upstash/ratelimit
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Legitimate intra-org Upstash maintainer transition; publisher has clean track record. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): cahidarda is a vetted Upstash maintainer with 78 approved packages. | ai | |
| dependencies | unvetted-dep:@upstash/core-analytics | AI (dependencies): @upstash/core-analytics is a first-party Upstash package used internally by @upstash/ratelimit for analytics; this dependency relationship is stable and expected across versions. | ai | |
| provenance | no-provenance | AI (provenance): Established Upstash package with 997k weekly downloads and 1450 days of history; lack of provenance is common and not a meaningful risk signal here. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 2.0.8 | 1 / 7 | |
| 2.0.7 | 1 / 7 | |
| 2.0.6 | 1 / 7 | |
| 2.0.5 | 1 / 7 | |
| 2.0.4 | 1 / 8 | |
| 2.0.3 | 1 / 6 | |
| 2.0.2 | 1 / 6 | |
| 2.0.1 | 1 / 6 | |
| 2.0.0 | 1 / 6 |
v2.0.5
2 findingsThis version was published by a different npm account than previous versions on 2024-12-05. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
2 findingsThis version was published by a different npm account than previous versions on 2024-10-23. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
2 findingsThis version was published by a different npm account than previous versions on 2024-09-16. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.