ui5-tooling-modules
UI5 CLI extensions to load and convert node modules as UI5 AMD-like modules
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:handlebars | AI (dependencies): Handlebars is a well-known templating library; stable dependency for this package across versions. | ai | |
| phantom-deps | phantom-dep:@rollup/pluginutils | AI (phantom-deps): @rollup/pluginutils is a listed runtime dependency in package.json; phantom-dep is a false positive here. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): Long-standing postinstall for UI5 tooling setup; SLSA provenance confirms CI/CD origin. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require on pkgJsonPath is a package.json loader pattern, not arbitrary code execution. | ai | |
| bogus-package | bogus-package | AI (bogus-package): ui5-community-bot is a known automation publisher for the ui5-ecosystem-showcase monorepo; templated naming is expected. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 3.36.0 | 22 / 2 | |
| 3.35.1 | 22 / 2 | |
| 3.34.4 | 21 / 2 | |
| 3.33.1 | 21 / 2 | |
| 3.32.3 | 21 / 2 | |
| 3.32.1 | 21 / 2 | |
| 3.32.0 | 21 / 2 | |
| 3.31.1 | 21 / 2 | |
| 3.30.8 | 21 / 2 | |
| 3.30.6 | 21 / 2 | |
| 3.30.4 | 21 / 2 | |
| 3.30.2 | 21 / 2 | |
| 3.30.1 | 21 / 2 | |
| 3.29.1 | 21 / 2 | |
| 3.27.7 | 18 / 2 | |
| 3.27.6 | 18 / 2 | |
| 3.27.3 | 18 / 2 | |
| 3.27.2 | 18 / 2 | |
| 3.27.0 | 18 / 2 | |
| 3.26.0 | 18 / 2 |
v3.36.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.35.1
2 findingsScript: node ./lib/postinstall.js
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.34.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.33.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.32.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.32.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.31.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.30.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.30.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.30.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.30.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.30.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.29.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.27.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.27.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.27.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.27.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.