← Home

@ui5/task-adaptation

npm Repository Homepage

Custom task for ui5-builder which allows building UI5 Flexibility Adaptation Projects for SAP BTP, Cloud Foundry environment

19
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

sap-ospo-adminui5-bot

Keywords

adaptationui5buildertoolsbusinessapplicationstudio

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): sap-ospo-admin is SAP's org-level admin account; consistent with SAP ecosystem governance, not a takeover signal. ai
maintainer-change maintainer-removed AI (maintainer-change): Removal of flovogt alongside sap-ospo-admin addition is consistent with SAP internal maintainer rotation. ai
phantom-deps phantom-dep:@sap-ux/store AI (phantom-deps): Declared but not directly imported; likely used via config/peer dependency pattern in SAP UX tooling. ai

Versions (showing 19 of 19)

Version Deps Published
1.6.6 16 / 36
1.6.5 16 / 36
1.6.4 15 / 37
1.6.3 15 / 37
1.6.2 15 / 38
1.6.1 15 / 38
1.6.0 15 / 38
1.5.4 15 / 38
1.5.3 16 / 38
1.5.2 16 / 38
1.5.1 16 / 34
1.5.0 16 / 34
1.4.3 15 / 34
1.4.2 15 / 36
1.4.1 15 / 36
1.4.0 14 / 36
1.3.3 14 / 36
1.3.2 10 / 36
1.3.0 10 / 36

v1.6.6

1 finding
LOW No provenance attestation provenance

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

v1.6.5

1 finding
LOW No provenance attestation provenance

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

v1.4.3

1 finding
LOW No provenance attestation provenance

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

v1.4.2

1 finding
LOW No provenance attestation provenance

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

v1.4.1

1 finding
LOW No provenance attestation provenance

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

v1.4.0

1 finding
LOW No provenance attestation provenance

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

v1.3.3

1 finding
LOW No provenance attestation provenance

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

v1.3.2

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.

v1.3.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.