← Home

@ui5/builder

npm Repository Homepage
22
Versions
—
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

openui5sapui5ui5builddevelopmenttool

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:base64-decode AI (semgrep): Decodes inline base64 source maps in bundle builder; not a payload risk. ai
semgrep semgrep:dynamic-require AI (semgrep): Loads jsdoc template utility from a resolved template path; stable pattern in this package. ai

Versions (showing 22 of 22)

Version Deps Published
4.2.0 15 / 21
4.1.6 15 / 21
4.1.5 15 / 21
4.1.4 15 / 21
4.1.3 15 / 21
4.1.2 15 / 21
4.1.1 15 / 21
4.1.0 15 / 21
4.0.13 15 / 21
4.0.12 15 / 21
4.0.11 15 / 21
4.0.10 15 / 21
4.0.9 15 / 21
4.0.8 15 / 21
4.0.7 15 / 21
4.0.6 15 / 21
4.0.5 15 / 21
4.0.4 15 / 21
4.0.3 16 / 20
4.0.2 16 / 20
4.0.1 16 / 18
4.0.0 16 / 18

v4.0.6

1 finding
LOW No provenance attestation provenance

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

v4.0.5

1 finding
LOW No provenance attestation provenance

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

v4.0.4

1 finding
LOW No provenance attestation provenance

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

v4.0.3

1 finding
LOW No provenance attestation provenance

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

v4.0.2

1 finding
LOW No provenance attestation provenance

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

v4.0.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.

v4.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.