@sapui5/sap.fe.placeholder
SAPUI5 Library sap.fe.placeholder
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
Versions (showing 60 of 160)
| Version | Deps | Published |
|---|---|---|
| 1.120.40 | 0 / 0 | |
| 1.120.39 | 0 / 0 | |
| 1.120.38 | 0 / 0 | |
| 1.120.37 | 0 / 0 | |
| 1.120.36 | 0 / 0 | |
| 1.120.35 | 0 / 0 | |
| 1.120.34 | 0 / 0 | |
| 1.120.33 | 0 / 0 | |
| 1.120.32 | 0 / 0 | |
| 1.120.31 | 0 / 0 | |
| 1.120.30 | 0 / 0 | |
| 1.120.29 | 0 / 0 | |
| 1.120.28 | 0 / 0 | |
| 1.120.27 | 0 / 0 | |
| 1.120.26 | 0 / 0 | |
| 1.120.25 | 0 / 0 | |
| 1.120.24 | 0 / 0 | |
| 1.120.23 | 0 / 0 | |
| 1.120.22 | 0 / 0 | |
| 1.120.21 | 0 / 0 | |
| 1.120.20 | 0 / 0 | |
| 1.120.19 | 0 / 0 | |
| 1.120.18 | 0 / 0 | |
| 1.120.17 | 0 / 0 | |
| 1.120.16 | 0 / 0 | |
| 1.120.15 | 0 / 0 | |
| 1.120.14 | 0 / 0 | |
| 1.120.13 | 0 / 0 | |
| 1.120.12 | 0 / 0 | |
| 1.120.11 | 0 / 0 | |
| 1.120.10 | 0 / 0 | |
| 1.108.41 | 0 / 3 | |
| 1.108.40 | 0 / 3 | |
| 1.108.39 | 0 / 3 | |
| 1.108.38 | 0 / 3 | |
| 1.108.37 | 0 / 3 | |
| 1.108.36 | 0 / 3 | |
| 1.108.35 | 0 / 3 | |
| 1.108.34 | 0 / 3 | |
| 1.108.33 | 0 / 3 | |
| 1.108.32 | 0 / 3 | |
| 1.108.31 | 0 / 3 | |
| 1.108.30 | 0 / 3 | |
| 1.108.29 | 0 / 3 | |
| 1.108.28 | 0 / 3 | |
| 1.108.27 | 0 / 3 | |
| 1.108.26 | 0 / 3 | |
| 1.108.25 | 0 / 3 | |
| 1.108.24 | 0 / 3 | |
| 1.108.23 | 0 / 3 | |
| 1.96.35 | 0 / 2 | |
| 1.96.34 | 0 / 2 | |
| 1.96.33 | 0 / 2 | |
| 1.96.32 | 0 / 2 | |
| 1.96.31 | 0 / 2 | |
| 1.96.30 | 0 / 2 | |
| 1.96.29 | 0 / 2 | |
| 1.96.28 | 0 / 2 | |
| 1.96.27 | 0 / 2 | |
| 1.96.26 | 0 / 2 |
v1.120.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.120.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.120.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.120.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.120.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.120.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.120.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.120.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.120.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.120.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.120.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.120.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.120.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.120.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.120.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.108.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.108.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.108.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.108.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.108.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.108.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.108.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.108.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.108.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.96.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.96.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.96.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.