@sap-ux/ui5-library-sub-generator
Generator for creating UI5 libraries
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:@sap-ux/ui5-info | AI (dependencies): First-party SAP UX tooling dep from the same open-ux-tools monorepo. | ai | |
| dependencies | unvetted-dep:yeoman-generator | AI (dependencies): Well-known Yeoman core package; expected for a Yeoman-based generator. | ai | |
| dependencies | unvetted-dep:@sap-ux/nodejs-utils | AI (dependencies): First-party SAP UX tooling dep from the same open-ux-tools monorepo. | ai | |
| dependencies | unvetted-dep:@sap-devx/yeoman-ui-types | AI (dependencies): SAP DevX type definitions for Yeoman UI; expected for this generator. | ai | |
| dependencies | unvetted-dep:@sap-ux/ui5-library-writer | AI (dependencies): First-party SAP UX tooling dep from the same open-ux-tools monorepo. | ai | |
| dependencies | unvetted-dep:@sap-ux/fiori-tools-settings | AI (dependencies): First-party SAP UX tooling dep from the same open-ux-tools monorepo. | ai | |
| dependencies | unvetted-dep:@sap-ux/ui5-library-inquirer | AI (dependencies): First-party SAP UX tooling dep from the same open-ux-tools monorepo. | ai | |
| dependencies | unvetted-dep:@sap-ux/fiori-generator-shared | AI (dependencies): First-party SAP UX tooling dep from the same open-ux-tools monorepo. | ai | |
| provenance | no-provenance | AI (provenance): Large SAP monorepo; lack of Sigstore provenance is common for enterprise npm packages. | ai |
Versions (showing 51 of 151)
| Version | Deps | Published |
|---|---|---|
| 0.1.45 | 9 / 11 | |
| 0.1.44 | 9 / 11 | |
| 0.1.43 | 9 / 11 | |
| 0.1.42 | 9 / 11 | |
| 0.1.41 | 9 / 11 | |
| 0.1.40 | 9 / 11 | |
| 0.1.39 | 9 / 11 | |
| 0.1.38 | 9 / 11 | |
| 0.1.37 | 9 / 11 | |
| 0.1.36 | 9 / 11 | |
| 0.1.35 | 9 / 11 | |
| 0.1.34 | 9 / 11 | |
| 0.1.33 | 9 / 11 | |
| 0.1.32 | 9 / 11 | |
| 0.1.31 | 9 / 11 | |
| 0.1.30 | 9 / 11 | |
| 0.1.29 | 9 / 11 | |
| 0.1.28 | 9 / 11 | |
| 0.1.27 | 9 / 11 | |
| 0.1.26 | 9 / 11 | |
| 0.1.25 | 9 / 11 | |
| 0.1.24 | 9 / 11 | |
| 0.1.23 | 9 / 11 | |
| 0.1.22 | 9 / 11 | |
| 0.1.21 | 9 / 11 | |
| 0.1.20 | 9 / 11 | |
| 0.1.19 | 9 / 11 | |
| 0.1.18 | 9 / 11 | |
| 0.1.17 | 9 / 11 | |
| 0.1.16 | 9 / 11 | |
| 0.1.15 | 9 / 11 | |
| 0.1.14 | 9 / 11 | |
| 0.1.13 | 9 / 11 | |
| 0.1.12 | 9 / 11 | |
| 0.1.11 | 9 / 11 | |
| 0.1.10 | 9 / 11 | |
| 0.1.9 | 9 / 11 | |
| 0.1.8 | 9 / 11 | |
| 0.1.7 | 9 / 11 | |
| 0.1.6 | 9 / 11 | |
| 0.1.5 | 9 / 11 | |
| 0.1.4 | 9 / 11 | |
| 0.1.3 | 9 / 11 | |
| 0.1.2 | 9 / 11 | |
| 0.1.1 | 9 / 11 | |
| 0.1.0 | 9 / 11 | |
| 0.0.90 | 9 / 11 | |
| 0.0.89 | 9 / 11 | |
| 0.0.88 | 9 / 11 | |
| 0.0.87 | 9 / 11 | |
| 0.0.86 | 9 / 11 |
v0.1.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.15
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.14
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.13
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.12
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.11
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.10
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.9
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.8
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.7
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.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.90
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.89
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.88
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.87
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.86
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.