@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 — the axios compromise (March 2026) relied on exactly this gap.
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 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 1.17.2 | 3 / 2 | |
| 1.17.0 | 3 / 1 | |
| 1.16.2 | 3 / 1 | |
| 1.16.1 | 3 / 1 | |
| 1.16.0 | 3 / 1 | |
| 1.15.0 | 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 |
v1.17.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: temporal-sdk-team.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: temporal-sdk-team.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.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.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.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.11.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.