@sapui5/sap.insights
SAPUI5 Library sap.insights
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 |
|---|---|---|---|---|
| source-diff | large-new-source-files | AI (source-diff): SAP UI5 library; size growth reflects legitimate library content additions across versions. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Diff is against a much newer version (1.142.3); size difference reflects branch divergence, not injection. | ai |
Versions (showing 51 of 99)
| Version | Deps | Published |
|---|---|---|
| 1.150.0 | 0 / 0 | |
| 1.149.0 | 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.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.6 | 0 / 0 | |
| 1.142.5 | 0 / 0 | |
| 1.142.4 | 0 / 0 | |
| 1.142.3 | 0 / 0 | |
| 1.142.1 | 0 / 0 | |
| 1.142.0 | 0 / 0 | |
| 1.141.0 | 0 / 0 | |
| 1.140.0 | 0 / 0 | |
| 1.139.2 | 0 / 0 | |
| 1.139.1 | 0 / 0 | |
| 1.139.0 | 0 / 0 | |
| 1.138.0 | 0 / 0 | |
| 1.136.13 | 0 / 0 | |
| 1.136.12 | 0 / 0 | |
| 1.136.11 | 0 / 0 | |
| 1.136.10 | 0 / 0 | |
| 1.136.8 | 0 / 0 | |
| 1.136.7 | 0 / 0 | |
| 1.136.6 | 0 / 0 | |
| 1.136.5 | 0 / 0 | |
| 1.136.4 | 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.0 | 0 / 0 | |
| 1.132.0 | 0 / 0 | |
| 1.131.0 | 0 / 0 | |
| 1.130.9 | 0 / 0 | |
| 1.130.8 | 0 / 0 | |
| 1.130.7 | 0 / 0 | |
| 1.130.6 | 0 / 0 | |
| 1.130.5 | 0 / 0 | |
| 1.130.4 | 0 / 0 | |
| 1.130.3 | 0 / 0 | |
| 1.130.2 | 0 / 0 | |
| 1.130.1 | 0 / 0 |
v1.150.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.149.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.148.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.148.1
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.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.7
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.2
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.