@sap-ux/ui5-application-writer
Writer module allowing to create a the base UI5 project structure.
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:mem-fs-editor | AI (dependencies): mem-fs-editor is a standard utility dependency pinned to a specific version; stable false positive for this package. | ai | |
| provenance | publisher-changed | AI (provenance): SAP migrated publishing to GitHub Actions CI/CD with SLSA attestation; stable pattern for this org. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): sap-ospo-admin is SAP's open-source admin account; consistent with org-level maintainer management. | ai | |
| provenance | no-provenance | AI (provenance): Long-established SAP UX package; lack of provenance is consistent across all 211 versions. | ai |
Versions (showing 73 of 73)
| Version | Deps | Published |
|---|---|---|
| 2.1.2 | 8 / 9 | |
| 2.1.1 | 8 / 9 | |
| 2.1.0 | 8 / 9 | |
| 2.0.8 | 8 / 9 | |
| 2.0.7 | 8 / 9 | |
| 2.0.6 | 8 / 9 | |
| 2.0.5 | 8 / 9 | |
| 2.0.4 | 8 / 9 | |
| 2.0.3 | 8 / 9 | |
| 2.0.2 | 8 / 9 | |
| 2.0.1 | 8 / 9 | |
| 2.0.0 | 8 / 9 | |
| 1.9.2 | 8 / 9 | |
| 1.9.1 | 8 / 9 | |
| 1.9.0 | 8 / 9 | |
| 1.8.8 | 8 / 9 | |
| 1.8.7 | 8 / 9 | |
| 1.8.6 | 8 / 9 | |
| 1.8.5 | 8 / 9 | |
| 1.8.4 | 8 / 9 | |
| 1.8.3 | 8 / 9 | |
| 1.8.1 | 8 / 9 | |
| 1.7.20 | 8 / 9 | |
| 1.7.19 | 8 / 9 | |
| 1.7.17 | 8 / 9 | |
| 1.7.15 | 8 / 9 | |
| 1.7.11 | 8 / 9 | |
| 1.7.10 | 8 / 9 | |
| 1.7.7 | 8 / 9 | |
| 1.7.6 | 8 / 9 | |
| 1.7.4 | 8 / 9 | |
| 1.7.3 | 8 / 9 | |
| 1.7.2 | 8 / 9 | |
| 1.6.8 | 8 / 9 | |
| 1.6.6 | 8 / 9 | |
| 1.6.5 | 8 / 9 | |
| 1.6.1 | 8 / 9 | |
| 1.5.18 | 8 / 9 | |
| 1.5.15 | 8 / 9 | |
| 1.5.13 | 8 / 9 | |
| 1.5.10 | 8 / 9 | |
| 1.5.8 | 8 / 9 | |
| 1.5.5 | 8 / 9 | |
| 1.5.4 | 8 / 9 | |
| 1.5.3 | 8 / 9 | |
| 1.5.1 | 8 / 9 | |
| 1.4.3 | 8 / 9 | |
| 1.4.2 | 8 / 9 | |
| 1.4.1 | 8 / 9 | |
| 1.4.0 | 8 / 9 | |
| 1.3.3 | 8 / 9 | |
| 1.3.2 | 8 / 9 | |
| 1.3.1 | 8 / 9 | |
| 1.3.0 | 8 / 9 | |
| 1.2.10 | 8 / 9 | |
| 1.2.9 | 8 / 9 | |
| 1.2.8 | 8 / 9 | |
| 1.2.7 | 8 / 9 | |
| 1.2.6 | 8 / 9 | |
| 1.2.5 | 8 / 9 | |
| 1.2.4 | 8 / 9 | |
| 1.2.3 | 8 / 9 | |
| 1.2.2 | 8 / 9 | |
| 1.2.1 | 8 / 9 | |
| 1.2.0 | 8 / 9 | |
| 1.1.6 | 8 / 9 | |
| 1.1.5 | 8 / 9 | |
| 1.1.4 | 8 / 9 | |
| 1.1.3 | 8 / 9 | |
| 1.1.2 | 8 / 9 | |
| 1.1.1 | 8 / 9 | |
| 1.1.0 | 8 / 9 | |
| 1.0.0 | 8 / 9 |
v2.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.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.
v1.0.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.