@sap-ux/fiori-app-sub-generator
A yeoman (sub) generator that can generate Fiori applications. Not for standalone use.
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/fiori-freestyle-writer | AI (dependencies): Same SAP/open-ux-tools monorepo scope; stable dependency. | ai | |
| dependencies | unvetted-dep:@sap-ux/annotation-converter | AI (dependencies): Same SAP/open-ux-tools monorepo scope; stable dependency. | ai | |
| dependencies | unvetted-dep:@sap-ux/fiori-tools-settings | AI (dependencies): Same SAP/open-ux-tools monorepo scope; stable dependency. | ai | |
| dependencies | unvetted-dep:@sap-ux/fiori-elements-writer | AI (dependencies): Same SAP/open-ux-tools monorepo scope; stable dependency. | ai | |
| provenance | no-provenance | AI (provenance): SAP open-ux-tools monorepo does not currently publish Sigstore provenance; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:mem-fs-editor | AI (dependencies): Well-known yeoman ecosystem dep; stable usage across many versions of this package. | ai | |
| dependencies | unvetted-dep:@sap-ux/ui5-info | AI (dependencies): Same SAP/open-ux-tools monorepo scope; stable dependency. | ai | |
| dependencies | unvetted-dep:@sap-ux/btp-utils | AI (dependencies): Same SAP/open-ux-tools monorepo scope; stable dependency. | ai | |
| dependencies | unvetted-dep:@sap-ux/edmx-parser | AI (dependencies): Same SAP/open-ux-tools monorepo scope; stable dependency. | ai | |
| dependencies | unvetted-dep:@sap-ux/feature-toggle | AI (dependencies): Same SAP/open-ux-tools monorepo scope; stable dependency. | ai | |
| dependencies | unvetted-dep:@sap-ux/axios-extension | AI (dependencies): Same SAP/open-ux-tools monorepo scope; stable dependency. | ai | |
| dependencies | unvetted-dep:@sap/service-provider-apis | AI (dependencies): SAP-published package; stable dependency in this package. | ai | |
| phantom-deps | phantom-dep:@sap/service-provider-apis | AI (phantom-deps): Used via config/type references in SAP monorepo; stable false positive. | ai | |
| phantom-deps | phantom-dep:@sap-ux/annotation-generator | AI (phantom-deps): Same-org sibling dep; phantom detection is a false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:mem-fs | AI (phantom-deps): mem-fs is a peer/indirect dep used by mem-fs-editor; phantom detection is a false positive for this package. | ai |
Versions (showing 51 of 98)
| Version | Deps | Published |
|---|---|---|
| 0.14.1 | 27 / 19 | |
| 0.14.0 | 27 / 19 | |
| 0.13.33 | 27 / 19 | |
| 0.13.29 | 27 / 19 | |
| 0.13.27 | 27 / 19 | |
| 0.13.11 | 27 / 19 | |
| 0.13.10 | 27 / 19 | |
| 0.11.98 | 27 / 19 | |
| 0.11.97 | 27 / 19 | |
| 0.11.96 | 27 / 19 | |
| 0.11.95 | 27 / 19 | |
| 0.11.94 | 27 / 19 | |
| 0.11.93 | 27 / 19 | |
| 0.11.92 | 27 / 19 | |
| 0.11.91 | 27 / 19 | |
| 0.11.90 | 27 / 19 | |
| 0.11.89 | 27 / 19 | |
| 0.11.88 | 27 / 19 | |
| 0.11.87 | 27 / 19 | |
| 0.11.86 | 27 / 19 | |
| 0.11.85 | 27 / 19 | |
| 0.11.84 | 27 / 19 | |
| 0.11.83 | 27 / 19 | |
| 0.11.82 | 27 / 19 | |
| 0.11.81 | 27 / 19 | |
| 0.11.80 | 27 / 19 | |
| 0.11.79 | 27 / 19 | |
| 0.11.78 | 27 / 19 | |
| 0.11.77 | 27 / 19 | |
| 0.11.75 | 27 / 19 | |
| 0.11.73 | 27 / 19 | |
| 0.11.72 | 27 / 19 | |
| 0.11.71 | 27 / 19 | |
| 0.11.70 | 27 / 19 | |
| 0.11.69 | 27 / 19 | |
| 0.11.67 | 27 / 19 | |
| 0.11.66 | 27 / 19 | |
| 0.11.65 | 27 / 19 | |
| 0.11.64 | 27 / 19 | |
| 0.11.63 | 27 / 19 | |
| 0.11.62 | 27 / 19 | |
| 0.11.61 | 27 / 19 | |
| 0.11.60 | 27 / 19 | |
| 0.11.59 | 27 / 19 | |
| 0.11.57 | 27 / 19 | |
| 0.11.56 | 27 / 19 | |
| 0.11.55 | 27 / 19 | |
| 0.11.54 | 27 / 19 | |
| 0.11.53 | 27 / 19 | |
| 0.11.52 | 27 / 19 | |
| 0.11.51 | 27 / 19 |
v0.14.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.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.11.98
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.97
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.96
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.95
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.94
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.93
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.92
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.91
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.90
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.89
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.88
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.87
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.86
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.85
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.84
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.83
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.82
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.81
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.80
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.79
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.78
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.77
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.75
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.73
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.72
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.71
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.70
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.69
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.67
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.66
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.64
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.63
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.62
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.61
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.60
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.59
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.57
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.54
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.