@sap-ux/ui-service-sub-generator
Generator for creating UI Service
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from human publisher to GitHub Actions CI/CD is confirmed by SLSA provenance attestation; stable for this SAP org package. | ai | |
| dependencies | unvetted-dep:@sap-ux/btp-utils | AI (dependencies): Same SAP org scope; sibling package in open-ux-tools monorepo. | ai | |
| dependencies | unvetted-dep:@sap-ux/system-access | AI (dependencies): Same SAP org scope; sibling package in open-ux-tools monorepo. | ai | |
| dependencies | unvetted-dep:@sap-ux/feature-toggle | AI (dependencies): Same SAP org scope; sibling package in open-ux-tools monorepo. | ai | |
| dependencies | unvetted-dep:@sap-ux/axios-extension | AI (dependencies): Same SAP org scope; sibling package in open-ux-tools monorepo. | ai | |
| dependencies | unvetted-dep:@sap-devx/yeoman-ui-types | AI (dependencies): SAP-devx org scope; standard SAP Fiori tooling dependency. | ai | |
| phantom-deps | phantom-dep:@sap-ux/logger | AI (phantom-deps): Same SAP org scope; phantom-dep heuristic false positive for monorepo transitive usage. | ai | |
| phantom-deps | phantom-dep:@sap-ux/inquirer-common | AI (phantom-deps): Same SAP org scope; phantom-dep heuristic false positive for monorepo transitive usage. | ai |
Versions (showing 61 of 262)
| Version | Deps | Published |
|---|---|---|
| 0.1.46 | 12 / 15 | |
| 0.1.45 | 12 / 15 | |
| 0.1.44 | 12 / 15 | |
| 0.1.43 | 12 / 15 | |
| 0.1.42 | 12 / 15 | |
| 0.1.41 | 12 / 15 | |
| 0.1.40 | 12 / 15 | |
| 0.1.39 | 12 / 15 | |
| 0.1.38 | 12 / 15 | |
| 0.1.37 | 12 / 15 | |
| 0.1.36 | 12 / 15 | |
| 0.1.35 | 12 / 15 | |
| 0.1.34 | 12 / 15 | |
| 0.1.33 | 12 / 15 | |
| 0.1.32 | 12 / 15 | |
| 0.1.31 | 12 / 15 | |
| 0.1.30 | 12 / 15 | |
| 0.1.29 | 12 / 15 | |
| 0.1.28 | 12 / 16 | |
| 0.1.27 | 12 / 16 | |
| 0.1.26 | 12 / 16 | |
| 0.1.25 | 12 / 16 | |
| 0.1.24 | 12 / 16 | |
| 0.1.23 | 12 / 16 | |
| 0.1.22 | 12 / 16 | |
| 0.1.21 | 12 / 16 | |
| 0.1.20 | 12 / 16 | |
| 0.1.19 | 12 / 16 | |
| 0.1.18 | 12 / 16 | |
| 0.1.17 | 12 / 16 | |
| 0.1.16 | 12 / 16 | |
| 0.1.15 | 12 / 16 | |
| 0.1.14 | 12 / 16 | |
| 0.1.13 | 12 / 16 | |
| 0.1.12 | 12 / 16 | |
| 0.1.11 | 12 / 16 | |
| 0.1.10 | 12 / 16 | |
| 0.1.9 | 12 / 16 | |
| 0.1.8 | 12 / 16 | |
| 0.1.7 | 12 / 16 | |
| 0.1.6 | 12 / 16 | |
| 0.1.5 | 12 / 16 | |
| 0.1.4 | 12 / 16 | |
| 0.1.3 | 12 / 16 | |
| 0.1.2 | 12 / 16 | |
| 0.1.1 | 12 / 16 | |
| 0.1.0 | 12 / 16 | |
| 0.0.42 | 12 / 16 | |
| 0.0.41 | 12 / 16 | |
| 0.0.40 | 12 / 16 | |
| 0.0.39 | 12 / 16 | |
| 0.0.38 | 12 / 16 | |
| 0.0.37 | 12 / 16 | |
| 0.0.36 | 12 / 16 | |
| 0.0.35 | 12 / 16 | |
| 0.0.34 | 12 / 16 | |
| 0.0.33 | 12 / 16 | |
| 0.0.32 | 12 / 16 | |
| 0.0.31 | 12 / 16 | |
| 0.0.30 | 12 / 16 | |
| 0.0.29 | 12 / 16 |
v0.1.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.