@upstash/workflow
Durable, Reliable and Performant Serverless Functions
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Package transitioned to GitHub Actions CI/CD publishing with SLSA provenance attestation; original author still listed in package.json. This is a legitimate automation adoption for an established Upstash package. | ai | |
| dependencies | unvetted-dep:@upstash/qstash | AI (dependencies): @upstash/qstash is the core Upstash messaging library that @upstash/workflow is explicitly built upon; this dependency is expected and legitimate for all versions of this package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.3.1 | 1 / 20 | |
| 1.3.0 | 1 / 20 | |
| 1.2.1 | 1 / 20 | |
| 1.2.0 | 1 / 20 | |
| 1.1.1 | 1 / 20 | |
| 1.1.0 | 1 / 20 | |
| 1.0.0 | 1 / 20 | |
| 0.2.23 | 4 / 22 | |
| 0.2.22 | 4 / 22 |
v1.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.