← Home

@ui5/webcomponents-compat

npm Repository Homepage

UI5 Web Components: webcomponents.compat

80
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

openui5sapui5ui5

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:dist/generated/templates/TableTemplate.lit.js AI (source-diff): Long lines are LitElement HTML template literals, not obfuscation; stable pattern for this package. ai
provenance publisher-changed AI (provenance): Migration to GitHub Actions CI/CD with SLSA provenance; legitimate SAP/UI5 org publishing pattern. ai

Versions (showing 80 of 80)

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

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

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.