@sap/hdi-deploy — Greenflagged

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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

sap_extncrepos

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
semgrep	semgrep:dynamic-require	AI (semgrep): Dynamic require loads peer-dep client package.json to read version — stable, benign pattern for this deployment tool.	ai	2026/05/22
semgrep	semgrep:child-process-import	AI (semgrep): HDI deploy tool legitimately uses child_process; consistent across all versions of this package.	ai	2026/05/22

Versions (showing 4 of 4)

Version	Deps	Published
5.6.1	6 / 0	2026-02-02
5.6.0	6 / 0	2025-12-04
5.5.1	6 / 0	2025-10-01
5.5.0	6 / 0	2025-07-28

v5.6.1

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.

v5.6.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.

v5.5.1

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.

v5.5.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.