@sap-ux/ui-service-inquirer
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 | no-provenance | AI (provenance): SAP open-ux-tools monorepo does not publish with Sigstore provenance; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@sap-ux/logger | AI (dependencies): SAP org package from the same open-ux-tools ecosystem; not a risk. | ai | |
| dependencies | unvetted-dep:yeoman-generator | AI (dependencies): Well-known Yeoman scaffolding library; not a risk. | ai | |
| dependencies | unvetted-dep:@sap-ux/btp-utils | AI (dependencies): SAP org package from the same open-ux-tools ecosystem; not a risk. | ai | |
| dependencies | unvetted-dep:@sap-ux/telemetry | AI (dependencies): SAP org package from the same open-ux-tools ecosystem; not a risk. | ai | |
| dependencies | unvetted-dep:@sap-ux/axios-extension | AI (dependencies): SAP org package from the same open-ux-tools ecosystem; not a risk. | ai | |
| dependencies | unvetted-dep:@sap-ux/inquirer-common | AI (dependencies): SAP org package from the same open-ux-tools ecosystem; not a risk. | ai | |
| dependencies | unvetted-dep:@sap-devx/yeoman-ui-types | AI (dependencies): SAP org package; not a risk. | ai | |
| dependencies | unvetted-dep:@sap-ux/guided-answers-helper | AI (dependencies): SAP org package from the same open-ux-tools ecosystem; not a risk. | ai | |
| dependencies | unvetted-dep:@sap-ux/odata-service-inquirer | AI (dependencies): SAP org package from the same open-ux-tools ecosystem; not a risk. | ai | |
| dependencies | unvetted-dep:@sap-ux/abap-deploy-config-inquirer | AI (dependencies): SAP org package from the same open-ux-tools ecosystem; not a risk. | ai |
Versions (showing 21 of 221)
| Version | Deps | Published |
|---|---|---|
| 0.1.6 | 11 / 14 | |
| 0.1.5 | 11 / 14 | |
| 0.1.4 | 11 / 14 | |
| 0.1.3 | 11 / 14 | |
| 0.1.2 | 11 / 14 | |
| 0.1.1 | 11 / 14 | |
| 0.1.0 | 11 / 14 | |
| 0.0.42 | 11 / 14 | |
| 0.0.41 | 11 / 14 | |
| 0.0.40 | 11 / 14 | |
| 0.0.39 | 11 / 14 | |
| 0.0.38 | 11 / 14 | |
| 0.0.37 | 11 / 14 | |
| 0.0.36 | 11 / 14 | |
| 0.0.35 | 11 / 14 | |
| 0.0.34 | 11 / 14 | |
| 0.0.33 | 11 / 14 | |
| 0.0.32 | 11 / 14 | |
| 0.0.31 | 11 / 14 | |
| 0.0.30 | 11 / 14 | |
| 0.0.29 | 11 / 14 |
v0.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.