@temporalio/ai-sdk
Temporal AI SDK integration 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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@temporalio/client | AI (phantom-deps): Same-org sibling dep declared in both runtime and devDeps; phantom-dep heuristic misfires for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established Temporal SDK team publisher; provenance gap is a process issue, not a security signal for this package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @temporalio/common is a first-party sibling package at the same version; not a suspicious third-party addition. | ai | |
| typosquat | typosquat.levenshtein:aws-sdk | AI (typosquat): Legitimate @temporalio scoped package; name reflects AI SDK integration, not aws-sdk impersonation. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 1.18.1 | 9 / 17 | |
| 1.18.0 | 9 / 17 | |
| 1.17.4 | 6 / 18 | |
| 1.17.3 | 9 / 17 | |
| 1.17.2 | 6 / 18 | |
| 1.17.1 | 6 / 0 | |
| 1.17.0 | 6 / 0 | |
| 1.16.2 | 6 / 0 | |
| 1.16.1 | 6 / 0 | |
| 1.16.0 | 6 / 0 | |
| 1.15.0 | 6 / 0 | |
| 1.14.1 | 5 / 0 | |
| 1.14.0 | 5 / 0 |
v1.18.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.1
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.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.
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.15.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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.