@sap-ux/fiori-freestyle-writer
SAP Fiori freestyle application writer
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 | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing is confirmed by SLSA provenance attestation; stable pattern for this SAP UX package. | ai | |
| phantom-deps | phantom-dep:mem-fs | AI (phantom-deps): mem-fs is a peer/indirect dep of mem-fs-editor; not directly imported but legitimately referenced in config. | ai |
Versions (showing 19 of 119)
| Version | Deps | Published |
|---|---|---|
| 2.0.18 | 12 / 8 | |
| 2.0.17 | 12 / 8 | |
| 2.0.16 | 12 / 8 | |
| 2.0.15 | 12 / 8 | |
| 2.0.14 | 12 / 8 | |
| 2.0.13 | 12 / 8 | |
| 2.0.12 | 12 / 8 | |
| 2.0.11 | 12 / 8 | |
| 2.0.10 | 12 / 8 | |
| 2.0.9 | 12 / 8 | |
| 2.0.8 | 12 / 8 | |
| 2.0.7 | 12 / 8 | |
| 2.0.6 | 12 / 8 | |
| 2.0.5 | 12 / 8 | |
| 2.0.4 | 12 / 8 | |
| 2.0.3 | 12 / 8 | |
| 2.0.2 | 11 / 8 | |
| 2.0.1 | 11 / 8 | |
| 2.0.0 | 11 / 8 |
v2.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.