← Home

@temporalio/ai-sdk

Temporal AI SDK integration package

26
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

mjameswhtemporal-sdk-team

Keywords

temporalworkflowaiai-sdkllmembeddings

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 26 of 26)

Version Deps Published
1.21.1 9 / 19
1.21.0 9 / 19
1.20.3 9 / 17
1.20.2 9 / 17
1.20.1 9 / 17
1.20.0 9 / 17
1.19.1 9 / 17
1.19.0 9 / 17
1.18.2 9 / 17
1.18.1 9 / 17
1.18.0 9 / 17
1.17.5 6 / 18
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.3 6 / 0
1.16.2 6 / 0
1.16.1 6 / 0
1.16.0 6 / 0
1.15.1 6 / 0
1.15.0 6 / 0
1.14.2 5 / 0
1.14.1 5 / 0
1.14.0 5 / 0

v1.21.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.21.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.20.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.20.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.20.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.20.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.19.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.19.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.18.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.17.5

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.16.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.15.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.14.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.