← Home

@ui5/webcomponents-base

npm Repository Homepage
85
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

openui5sapui5ui5

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:dist/prod/thirdparty/preact/preact.module.js AI (source-diff): Minified Preact library bundled as a third-party dependency; well-known open source code. ai
source-diff obfuscated-file:src/thirdparty/preact/preact.module.js AI (source-diff): Minified Preact library vendored in src/thirdparty; well-known open source code. ai
source-diff obfuscated-file:dist/thirdparty/preact/preact.module.js AI (source-diff): Minified Preact library bundled as a third-party dependency; well-known open source code. ai
source-diff obfuscated-file:dist/prod/util/ColorConversion.js AI (source-diff): Minified CSS color-name-to-hex lookup table; not obfuscated malicious code. Stable pattern for this package's prod build artifacts. ai
phantom-deps phantom-dep:chokidar-cli AI (phantom-deps): chokidar-cli is a dev/build tool misclassified as runtime dep; confirmed not directly imported. ai
source-diff obfuscated-file:dist/prod/index.js AI (source-diff): dist/prod/ is the standard production minified bundle for this SAP UI5 package; minification is expected and benign. ai
provenance publisher-changed AI (provenance): SAP migrated publishing to GitHub Actions CI/CD with SLSA attestation; publisher change is legitimate automation transition. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy flag is a false positive; package has 685 versions and active development history — likely a gap in npm download data or publishing cadence change. ai

Versions (showing 85 of 85)

Version Deps Published
2.24.0 2 / 13
2.23.3 2 / 13
2.23.2 2 / 13
2.23.1 2 / 13
2.23.0 2 / 13
2.22.1 2 / 13
2.22.0 2 / 13
2.21.2 2 / 13
2.21.1 2 / 13
2.21.0 2 / 13
2.20.5 2 / 13
2.20.4 2 / 13
2.20.3 2 / 13
2.20.2 2 / 13
2.20.1 2 / 13
2.20.0 2 / 13
2.19.4 2 / 13
2.19.3 2 / 13
2.19.2 2 / 13
2.19.1 2 / 13
2.19.0 2 / 13
2.18.2 2 / 13
2.18.1 2 / 13
2.18.0 2 / 13
2.17.2 2 / 13
2.17.1 2 / 13
2.17.0 2 / 13
2.16.3 2 / 16
2.16.2 2 / 16
2.16.1 2 / 16
2.16.0 2 / 16
2.15.5 3 / 15
2.15.4 3 / 15
2.15.3 3 / 15
2.15.2 3 / 15
2.15.1 3 / 15
2.15.0 3 / 15
2.14.1 2 / 13
2.14.0 2 / 13
2.13.8 2 / 12
2.13.7 2 / 12
2.13.6 2 / 12
2.13.5 2 / 12
2.13.4 2 / 12
2.13.3 2 / 12
2.13.2 2 / 12
2.13.1 2 / 12
2.13.0 2 / 12
2.12.0 2 / 12
2.11.0 2 / 12
2.10.1 2 / 12
2.10.0 2 / 12
2.9.0 2 / 12
2.8.0 2 / 11
2.7.7 2 / 11
2.7.6 2 / 11
2.7.5 2 / 11
2.7.4 2 / 11
2.7.3 2 / 11
2.7.2 2 / 11
2.7.1 2 / 11
2.7.0 2 / 11
2.6.3 2 / 11
2.6.2 2 / 11
2.6.1 2 / 11
2.6.0 2 / 11
2.5.3 2 / 11
2.5.2 2 / 11
2.5.1 2 / 11
2.5.0 2 / 11
2.4.2 2 / 11
2.4.1 2 / 11
2.4.0 2 / 11
2.3.0 2 / 11
2.2.0 2 / 11
2.1.2 2 / 11
2.1.1 2 / 11
2.1.0 2 / 11
2.0.1 2 / 11
2.0.0 2 / 11
1.24.29 2 / 10
1.24.28 2 / 10
1.24.27 2 / 10
1.24.26 2 / 10
1.24.25 2 / 10

v2.24.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.23.3

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

v2.8.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.

v2.7.4

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.

v2.7.3

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.

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

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

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

v2.6.3

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.

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

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

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

v2.5.3

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.

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

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

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

v2.4.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.

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

v2.2.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.

v2.1.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.

v2.1.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.

v2.1.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.

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

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.

v1.24.29

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.