@sapui5/ts-types-esm
SAPUI5 TypeScript Definitions - ES Modules
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/qunit | AI (phantom-deps): @types/* packages loaded by convention in TypeScript; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/three | AI (phantom-deps): @types/* packages loaded by convention in TypeScript; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/jquery | AI (phantom-deps): @types/* packages loaded by convention in TypeScript; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/offscreencanvas | AI (phantom-deps): @types/* packages loaded by convention in TypeScript; stable false positive for this package. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 1.148.1 | 4 / 0 | |
| 1.148.0 | 4 / 0 | |
| 1.147.2 | 4 / 0 | |
| 1.147.1 | 4 / 0 | |
| 1.147.0 | 4 / 0 | |
| 1.145.3 | 4 / 0 | |
| 1.145.2 | 4 / 0 | |
| 1.145.1 | 4 / 0 | |
| 1.142.13 | 4 / 0 | |
| 1.142.12 | 4 / 0 | |
| 1.142.11 | 4 / 0 | |
| 1.142.10 | 4 / 0 | |
| 1.136.18 | 4 / 0 | |
| 1.136.17 | 4 / 0 | |
| 1.120.46 | 4 / 0 | |
| 1.120.45 | 4 / 0 | |
| 1.120.44 | 4 / 0 | |
| 1.108.53 | 4 / 0 | |
| 1.108.52 | 4 / 0 | |
| 1.96.48 | 0 / 0 | |
| 1.96.47 | 0 / 0 |
v1.148.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.148.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.147.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.147.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.147.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.145.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.145.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.145.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.142.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.142.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.142.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.142.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.136.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.136.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.120.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.120.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.120.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.108.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.108.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.96.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.96.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.