@temporalio/nexus
Temporal.io SDK Nexus sub-package
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Official Temporal SDK sub-package published by temporal-sdk-team; lack of Sigstore attestation is a process gap, not a security risk for this well-established org. | ai | |
| typosquat | typosquat.levenshtein:next | AI (typosquat): @temporalio/nexus is a scoped Temporal SDK sub-package for Nexus RPC integration, not a typosquat of 'next'. The @temporalio namespace and Nexus feature name make this a stable false positive. | ai | |
| dependencies | unvetted-dep:@temporalio/proto | AI (dependencies): Sibling package from the same Temporal SDK monorepo; expected internal dependency at matching version. | ai | |
| dependencies | unvetted-dep:@temporalio/client | AI (dependencies): Sibling package from the same Temporal SDK monorepo; expected internal dependency at matching version. | ai | |
| dependencies | unvetted-dep:@temporalio/common | AI (dependencies): Sibling package from the same Temporal SDK monorepo; expected internal dependency at matching version. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.17.2 | 5 / 1 | |
| 1.17.0 | 5 / 0 | |
| 1.16.2 | 5 / 0 | |
| 1.16.1 | 5 / 0 | |
| 1.16.0 | 5 / 0 | |
| 1.15.0 | 5 / 0 | |
| 1.14.1 | 5 / 0 | |
| 1.14.0 | 5 / 0 | |
| 1.13.2 | 5 / 0 | |
| 1.13.1 | 5 / 0 | |
| 1.13.0 | 5 / 0 |
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 findingPackage 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.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.