@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 100 of 237)
| Version | Deps | Published |
|---|---|---|
| 0.1.50 | 9 / 11 | |
| 0.1.49 | 9 / 11 | |
| 0.1.48 | 9 / 11 | |
| 0.1.47 | 9 / 11 | |
| 0.1.46 | 9 / 11 | |
| 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 | |
| 0.0.85 | 9 / 11 | |
| 0.0.84 | 9 / 11 | |
| 0.0.83 | 9 / 11 | |
| 0.0.82 | 9 / 11 | |
| 0.0.81 | 9 / 11 | |
| 0.0.80 | 9 / 11 | |
| 0.0.79 | 9 / 11 | |
| 0.0.78 | 9 / 11 | |
| 0.0.77 | 9 / 12 | |
| 0.0.76 | 9 / 12 | |
| 0.0.75 | 9 / 12 | |
| 0.0.74 | 9 / 12 | |
| 0.0.73 | 9 / 12 | |
| 0.0.72 | 9 / 12 | |
| 0.0.71 | 9 / 12 | |
| 0.0.70 | 9 / 12 | |
| 0.0.69 | 9 / 12 | |
| 0.0.68 | 9 / 12 | |
| 0.0.67 | 9 / 12 | |
| 0.0.66 | 9 / 12 | |
| 0.0.65 | 9 / 12 | |
| 0.0.63 | 9 / 12 | |
| 0.0.62 | 9 / 12 | |
| 0.0.61 | 9 / 12 | |
| 0.0.60 | 9 / 12 | |
| 0.0.59 | 9 / 12 | |
| 0.0.58 | 9 / 12 | |
| 0.0.57 | 9 / 12 | |
| 0.0.56 | 9 / 12 | |
| 0.0.55 | 9 / 12 | |
| 0.0.54 | 9 / 12 | |
| 0.0.53 | 9 / 12 | |
| 0.0.52 | 9 / 12 | |
| 0.0.51 | 9 / 12 | |
| 0.0.50 | 9 / 12 | |
| 0.0.49 | 9 / 12 | |
| 0.0.48 | 9 / 12 | |
| 0.0.47 | 9 / 12 | |
| 0.0.46 | 9 / 12 | |
| 0.0.45 | 9 / 12 | |
| 0.0.44 | 9 / 12 | |
| 0.0.43 | 9 / 12 | |
| 0.0.42 | 9 / 12 | |
| 0.0.41 | 9 / 12 |
v0.0.85
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.84
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.83
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.82
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.81
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.80
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.79
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.78
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.77
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.76
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.75
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.74
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.73
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.72
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.71
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.70
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.69
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.68
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.67
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.66
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.65
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.63
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.62
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.61
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.60
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.59
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.58
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.57
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.56
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.55
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.54
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.53
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.52
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.51
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.50
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.49
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.48
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.47
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.46
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.45
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.44
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.43
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.