@temporalio/workflow
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@temporalio/common | AI (dependencies): First-party sibling package from the same Temporal SDK monorepo; always a legitimate dependency for this package. | ai | |
| dependencies | unvetted-dep:@temporalio/proto | AI (dependencies): First-party sibling package from the same Temporal SDK monorepo; always a legitimate dependency for this package. | ai | |
| dependencies | unvetted-dep:nexus-rpc | AI (dependencies): nexus-rpc is a legitimate Temporal Nexus RPC integration dependency; stable and expected for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established Temporal SDK package; lack of Sigstore provenance is common and not a risk signal for this well-known publisher. | ai |
Versions (showing 51 of 76)
| Version | Deps | Published |
|---|---|---|
| 1.21.1 | 3 / 2 | |
| 1.21.0 | 3 / 2 | |
| 1.20.3 | 3 / 2 | |
| 1.20.2 | 3 / 2 | |
| 1.20.1 | 3 / 2 | |
| 1.20.0 | 3 / 2 | |
| 1.19.1 | 3 / 2 | |
| 1.19.0 | 3 / 2 | |
| 1.18.2 | 3 / 2 | |
| 1.18.1 | 3 / 2 | |
| 1.18.0 | 3 / 2 | |
| 1.17.5 | 3 / 2 | |
| 1.17.4 | 3 / 2 | |
| 1.17.3 | 3 / 2 | |
| 1.17.2 | 3 / 2 | |
| 1.17.0 | 3 / 1 | |
| 1.16.3 | 3 / 1 | |
| 1.16.2 | 3 / 1 | |
| 1.16.1 | 3 / 1 | |
| 1.16.0 | 3 / 1 | |
| 1.15.1 | 3 / 1 | |
| 1.15.0 | 3 / 1 | |
| 1.14.2 | 3 / 1 | |
| 1.14.1 | 3 / 1 | |
| 1.14.0 | 3 / 1 | |
| 1.13.2 | 3 / 1 | |
| 1.13.1 | 3 / 1 | |
| 1.13.0 | 3 / 1 | |
| 1.12.3 | 2 / 1 | |
| 1.12.2 | 2 / 1 | |
| 1.12.1 | 2 / 1 | |
| 1.12.0 | 2 / 1 | |
| 1.11.8 | 2 / 1 | |
| 1.11.7 | 2 / 1 | |
| 1.11.6 | 2 / 1 | |
| 1.11.5 | 2 / 1 | |
| 1.11.4 | 2 / 1 | |
| 1.11.3 | 2 / 1 | |
| 1.11.2 | 2 / 1 | |
| 1.11.1 | 2 / 1 | |
| 1.11.0 | 2 / 1 | |
| 1.10.3 | 2 / 1 | |
| 1.10.2 | 2 / 1 | |
| 1.10.1 | 2 / 1 | |
| 1.10.0 | 2 / 1 | |
| 1.9.3 | 2 / 1 | |
| 1.9.2 | 2 / 1 | |
| 1.9.1 | 2 / 1 | |
| 1.9.0 | 2 / 1 | |
| 1.8.6 | 2 / 1 | |
| 1.8.5 | 2 / 1 |
v1.21.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.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.
v1.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (tempbearpig) than the most recent previously approved version (temporal-sdk-team) on 2024-02-06, but tempbearpig is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.