@upstash/qstash
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): 127.0.0.1 localhost reference for local port detection; not an exfiltration or C2 endpoint. | ai | |
| dependencies | unvetted-dep:neverthrow | AI (dependencies): neverthrow is a well-known TypeScript Result-type library with a strong ecosystem reputation; its use in a typed API client is entirely expected and benign. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 2.11.0 | 3 / 22 | |
| 2.10.1 | 3 / 22 | |
| 2.10.0 | 3 / 22 | |
| 2.9.1 | 3 / 22 | |
| 2.9.0 | 3 / 22 | |
| 2.8.4 | 3 / 23 | |
| 2.8.3 | 3 / 23 | |
| 2.8.2 | 3 / 23 | |
| 2.8.1 | 3 / 23 | |
| 2.8.0 | 3 / 23 |
v2.11.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.10.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.9.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.