@sap-ux/ui5-info
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI/CD publisher with SLSA attestation; consistent with SAP org-level automation. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): sap-ospo-admin is SAP's open-source admin account; expected for SAP org packages. | ai |
Versions (showing 48 of 48)
| Version | Deps | Published |
|---|---|---|
| 1.0.5 | 3 / 4 | |
| 1.0.4 | 3 / 4 | |
| 1.0.3 | 3 / 4 | |
| 1.0.2 | 3 / 4 | |
| 1.0.1 | 3 / 4 | |
| 1.0.0 | 3 / 4 | |
| 0.14.0 | 3 / 3 | |
| 0.13.21 | 3 / 3 | |
| 0.13.20 | 3 / 3 | |
| 0.13.19 | 3 / 3 | |
| 0.13.18 | 3 / 3 | |
| 0.13.17 | 3 / 3 | |
| 0.13.16 | 3 / 3 | |
| 0.13.15 | 3 / 3 | |
| 0.13.14 | 3 / 3 | |
| 0.13.13 | 3 / 3 | |
| 0.13.12 | 3 / 3 | |
| 0.13.11 | 3 / 3 | |
| 0.13.10 | 3 / 3 | |
| 0.13.9 | 3 / 3 | |
| 0.13.8 | 3 / 3 | |
| 0.13.7 | 3 / 3 | |
| 0.13.6 | 3 / 3 | |
| 0.13.5 | 3 / 3 | |
| 0.13.4 | 3 / 3 | |
| 0.13.3 | 3 / 3 | |
| 0.13.2 | 3 / 3 | |
| 0.13.1 | 3 / 3 | |
| 0.13.0 | 3 / 3 | |
| 0.12.4 | 3 / 3 | |
| 0.12.3 | 3 / 3 | |
| 0.12.2 | 3 / 3 | |
| 0.12.1 | 3 / 3 | |
| 0.12.0 | 3 / 3 | |
| 0.11.1 | 3 / 3 | |
| 0.11.0 | 3 / 3 | |
| 0.10.1 | 3 / 3 | |
| 0.10.0 | 3 / 3 | |
| 0.9.1 | 3 / 3 | |
| 0.9.0 | 3 / 3 | |
| 0.8.3 | 3 / 3 | |
| 0.8.2 | 3 / 3 | |
| 0.8.1 | 3 / 3 | |
| 0.8.0 | 3 / 3 | |
| 0.7.1 | 3 / 3 | |
| 0.7.0 | 3 / 3 | |
| 0.6.0 | 3 / 3 | |
| 0.5.0 | 3 / 3 |
v1.0.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.