@sapui5/sap.fe.plugins.managecache
SAPUI5 Library sap.fe.plugins.managecache
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 100 of 100)
| Version | Deps | Published |
|---|---|---|
| 1.150.0 | 0 / 0 | |
| 1.149.0 | 0 / 0 | |
| 1.148.4 | 0 / 0 | |
| 1.148.3 | 0 / 0 | |
| 1.148.2 | 0 / 0 | |
| 1.148.1 | 0 / 0 | |
| 1.148.0 | 0 / 0 | |
| 1.147.0 | 0 / 0 | |
| 1.146.0 | 0 / 0 | |
| 1.145.3 | 0 / 0 | |
| 1.145.2 | 0 / 0 | |
| 1.145.1 | 0 / 0 | |
| 1.145.0 | 0 / 0 | |
| 1.144.0 | 0 / 0 | |
| 1.143.0 | 0 / 0 | |
| 1.142.13 | 0 / 0 | |
| 1.142.11 | 0 / 0 | |
| 1.142.10 | 0 / 0 | |
| 1.142.9 | 0 / 0 | |
| 1.142.8 | 0 / 0 | |
| 1.142.7 | 0 / 0 | |
| 1.142.6 | 0 / 0 | |
| 1.142.5 | 0 / 0 | |
| 1.142.3 | 0 / 0 | |
| 1.142.2 | 0 / 0 | |
| 1.142.1 | 0 / 0 | |
| 1.142.0 | 0 / 0 | |
| 1.141.2 | 0 / 0 | |
| 1.141.1 | 0 / 0 | |
| 1.141.0 | 0 / 0 | |
| 1.140.0 | 0 / 0 | |
| 1.139.4 | 0 / 0 | |
| 1.139.1 | 0 / 0 | |
| 1.139.0 | 0 / 0 | |
| 1.138.0 | 0 / 0 | |
| 1.136.20 | 0 / 0 | |
| 1.136.19 | 0 / 0 | |
| 1.136.18 | 0 / 0 | |
| 1.136.17 | 0 / 0 | |
| 1.136.16 | 0 / 0 | |
| 1.136.15 | 0 / 0 | |
| 1.136.13 | 0 / 0 | |
| 1.136.12 | 0 / 0 | |
| 1.136.11 | 0 / 0 | |
| 1.136.10 | 0 / 0 | |
| 1.136.9 | 0 / 0 | |
| 1.136.8 | 0 / 0 | |
| 1.136.7 | 0 / 0 | |
| 1.136.6 | 0 / 0 | |
| 1.136.5 | 0 / 0 | |
| 1.136.3 | 0 / 0 | |
| 1.136.2 | 0 / 0 | |
| 1.136.1 | 0 / 0 | |
| 1.136.0 | 0 / 0 | |
| 1.135.0 | 0 / 0 | |
| 1.134.0 | 0 / 0 | |
| 1.133.4 | 0 / 0 | |
| 1.133.3 | 0 / 0 | |
| 1.133.2 | 0 / 0 | |
| 1.133.1 | 0 / 0 | |
| 1.133.0 | 0 / 0 | |
| 1.132.0 | 0 / 0 | |
| 1.131.0 | 0 / 0 | |
| 1.130.11 | 0 / 0 | |
| 1.130.10 | 0 / 0 | |
| 1.130.9 | 0 / 0 | |
| 1.130.8 | 0 / 0 | |
| 1.130.6 | 0 / 0 | |
| 1.130.5 | 0 / 0 | |
| 1.130.4 | 0 / 0 | |
| 1.130.3 | 0 / 0 | |
| 1.130.1 | 0 / 0 | |
| 1.130.0 | 0 / 0 | |
| 1.129.1 | 0 / 0 | |
| 1.129.0 | 0 / 0 | |
| 1.128.0 | 0 / 0 | |
| 1.127.6 | 0 / 0 | |
| 1.127.5 | 0 / 0 | |
| 1.127.4 | 0 / 0 | |
| 1.127.3 | 0 / 0 | |
| 1.127.2 | 0 / 0 | |
| 1.127.1 | 0 / 0 | |
| 1.127.0 | 0 / 0 | |
| 1.126.2 | 0 / 0 | |
| 1.126.1 | 0 / 0 | |
| 1.126.0 | 0 / 0 | |
| 1.125.0 | 0 / 0 | |
| 1.124.9 | 0 / 0 | |
| 1.124.8 | 0 / 0 | |
| 1.124.7 | 0 / 0 | |
| 1.124.6 | 0 / 0 | |
| 1.124.5 | 0 / 0 | |
| 1.124.4 | 0 / 0 | |
| 1.124.3 | 0 / 0 | |
| 1.124.2 | 0 / 0 | |
| 1.124.1 | 0 / 0 | |
| 1.124.0 | 0 / 0 | |
| 1.123.1 | 0 / 0 | |
| 1.121.6 | 0 / 0 | |
| 1.121.4 | 0 / 0 |
v1.150.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.148.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.148.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.142.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.135.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.134.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.133.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.133.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.132.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.131.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.130.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.130.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.130.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.130.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.130.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.130.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.130.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.130.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.129.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.129.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.128.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.127.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.127.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.127.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.127.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.127.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.127.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.127.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.126.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.126.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.126.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.125.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.124.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.124.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.124.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.124.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.124.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.124.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.124.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.124.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.124.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.124.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.123.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.121.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.121.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.