@ui5/server
UI5 CLI - Server
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:semver | AI (typosquat): Scoped SAP package @ui5/server; name similarity to 'semver' is coincidental, not a typosquat. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 4.0.15 | 19 / 21 | |
| 4.0.14 | 19 / 21 | |
| 4.0.13 | 19 / 21 | |
| 4.0.12 | 19 / 21 | |
| 4.0.11 | 19 / 21 | |
| 4.0.10 | 19 / 21 | |
| 4.0.9 | 19 / 21 | |
| 4.0.8 | 19 / 21 | |
| 4.0.7 | 19 / 21 | |
| 4.0.6 | 19 / 21 | |
| 4.0.5 | 19 / 21 | |
| 4.0.4 | 19 / 21 | |
| 4.0.3 | 19 / 21 | |
| 4.0.2 | 19 / 19 | |
| 4.0.1 | 19 / 19 | |
| 4.0.0 | 19 / 19 |
v4.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.