← Home

@sap-ai-sdk/orchestration

npm Repository Homepage

SAP Cloud SDK for AI is the official Software Development Kit (SDK) for **SAP AI Core**, **SAP Generative AI Hub**, and **Orchestration Service**.

12
Versions
Apache-2.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

marikanersap-ospo-adminjjtangzhongpinwangkavithasivadavidkna-sap

Keywords

sap-ai-sdkorchestrationllm-access

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@sap-ai-sdk/core AI (dependencies): Sibling package in the SAP AI SDK monorepo; published together at matching versions from the same CI/CD pipeline with SLSA provenance. ai
dependencies unvetted-dep:@sap-ai-sdk/ai-api AI (dependencies): Sibling package in the SAP AI SDK monorepo; published together at matching versions from the same CI/CD pipeline with SLSA provenance. ai
dependencies unvetted-dep:@sap-cloud-sdk/util AI (dependencies): Part of the SAP Cloud SDK ecosystem, a well-established SAP-maintained library used across the SAP SDK suite. ai
dependencies unvetted-dep:@sap-ai-sdk/prompt-registry AI (dependencies): Sibling package in the SAP AI SDK monorepo; published together at matching versions from the same CI/CD pipeline with SLSA provenance. ai

Versions (showing 12 of 12)

Version Deps Published
2.11.0 5 / 2
2.10.0 5 / 2
2.9.0 5 / 2
2.8.0 5 / 2
2.7.0 5 / 2
2.6.0 5 / 2
2.5.0 5 / 2
2.4.0 5 / 2
2.3.0 5 / 2
2.2.0 5 / 2
2.1.0 5 / 2
2.0.0 5 / 2

v2.11.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.10.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.9.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.8.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.7.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.6.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.5.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.4.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.3.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.2.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.1.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.