@ui5/project
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@ui5/fs | AI (dependencies): First-party SAP/UI5 sibling package; same publisher org, stable across all versions. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 4.0.17 | 21 / 24 | |
| 4.0.16 | 21 / 24 | |
| 4.0.15 | 21 / 24 | |
| 4.0.14 | 21 / 24 | |
| 4.0.13 | 21 / 24 | |
| 4.0.12 | 21 / 24 | |
| 4.0.11 | 21 / 24 | |
| 4.0.10 | 21 / 24 | |
| 4.0.9 | 21 / 24 | |
| 4.0.8 | 21 / 24 | |
| 4.0.7 | 21 / 24 | |
| 4.0.6 | 21 / 24 | |
| 4.0.5 | 21 / 24 | |
| 4.0.4 | 21 / 24 | |
| 4.0.3 | 22 / 23 | |
| 4.0.2 | 22 / 21 | |
| 4.0.1 | 22 / 21 | |
| 4.0.0 | 22 / 21 |
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. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.