← Home

@ui5/webcomponents-theming

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/generated/themes/sap_horizon_hcw_exp/parameters-bundle.css.js AI (source-diff): Long-line CSS variable bundle generated from SAP theming engine; not executable obfuscation. ai
source-diff obfuscated-file:dist/generated/themes/sap_belize/parameters-bundle.css.js AI (source-diff): Long-line CSS variable bundle generated from SAP theming engine; not executable obfuscation. ai
source-diff obfuscated-file:dist/generated/themes/sap_horizon_dark_exp/parameters-bundle.css.js AI (source-diff): Long-line CSS variable bundle generated from SAP theming engine; not executable obfuscation. ai
source-diff obfuscated-file:dist/generated/themes/sap_horizon_exp/parameters-bundle.css.js AI (source-diff): Long-line CSS variable bundle generated from SAP theming engine; not executable obfuscation. ai
source-diff obfuscated-file:dist/generated/themes/sap_horizon_hcb_exp/parameters-bundle.css.js AI (source-diff): Long-line CSS variable bundle generated from SAP theming engine; not executable obfuscation. ai
source-diff obfuscated-file:dist/generated/themes/sap_belize_hcb/parameters-bundle.css.js AI (source-diff): Long-line CSS variable bundle generated from SAP theming engine; not executable obfuscation. ai
source-diff obfuscated-file:dist/generated/themes/sap_belize_hcw/parameters-bundle.css.js AI (source-diff): Long-line CSS variable bundle generated from SAP theming engine; not executable obfuscation. ai
source-diff obfuscated-file:dist/generated/themes/sap_horizon_auto/parameters-bundle.css.d.ts AI (source-diff): Long-line TypeScript declaration wrapping CSS theme variables; not obfuscation, stable pattern for this theming package. ai
source-diff obfuscated-file:dist/generated/themes/sap_horizon_hc_auto/parameters-bundle.css.d.ts AI (source-diff): Same pattern: CSS custom property bundle in a .d.ts declaration; benign for this theming package. ai
provenance publisher-changed AI (provenance): Transition from ui5-webc-bot to GitHub Actions with SLSA attestation indicates legitimate CI/CD migration, not compromise. ai
phantom-deps phantom-dep:@sap-theming/theming-base-content AI (phantom-deps): SAP theming content package used via config/build tooling, not direct import; stable false positive for this package. ai

Versions (showing 85 of 85)

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

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.