@sap-ux/cf-deploy-config-writer
Add or amend Cloud Foundry and ABAP deployment configuration for SAP projects
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:hasbin | AI (dependencies): Standard utility dep for a SAP deploy tooling package; no malicious indicators. | ai | |
| dependencies | unvetted-dep:@sap-ux/yaml | AI (dependencies): SAP UX ecosystem dep; expected for this package. | ai | |
| dependencies | unvetted-dep:@sap/mta-lib | AI (dependencies): SAP MTA tooling dep; expected for CF deploy config writer. | ai | |
| dependencies | unvetted-dep:@sap/cf-tools | AI (dependencies): SAP CF tooling dep; expected for CF deploy config writer. | ai | |
| dependencies | unvetted-dep:mem-fs-editor | AI (dependencies): Well-known Yeoman ecosystem dep; no risk. | ai | |
| dependencies | unvetted-dep:@sap-ux/btp-utils | AI (dependencies): SAP UX ecosystem dep; expected for this package. | ai | |
| dependencies | unvetted-dep:@sap-ux/ui5-config | AI (dependencies): SAP UX ecosystem dep; expected for this package. | ai | |
| dependencies | unvetted-dep:@sap-ux/nodejs-utils | AI (dependencies): SAP UX ecosystem dep; expected for this package. | ai | |
| provenance | no-provenance | AI (provenance): SAP UX packages consistently lack Sigstore provenance; stable false positive for this org. | ai |
Versions (showing 51 of 103)
| Version | Deps | Published |
|---|---|---|
| 0.3.106 | 14 / 11 | |
| 0.3.105 | 14 / 11 | |
| 0.3.101 | 14 / 11 | |
| 0.3.100 | 14 / 11 | |
| 0.3.99 | 14 / 11 | |
| 0.3.98 | 14 / 11 | |
| 0.3.97 | 14 / 11 | |
| 0.3.96 | 14 / 11 | |
| 0.3.95 | 14 / 11 | |
| 0.3.94 | 14 / 11 | |
| 0.3.93 | 14 / 11 | |
| 0.3.92 | 14 / 11 | |
| 0.3.91 | 14 / 11 | |
| 0.3.90 | 14 / 11 | |
| 0.3.89 | 14 / 11 | |
| 0.3.88 | 14 / 11 | |
| 0.3.87 | 14 / 11 | |
| 0.3.86 | 14 / 11 | |
| 0.3.85 | 14 / 11 | |
| 0.3.84 | 14 / 11 | |
| 0.3.83 | 14 / 11 | |
| 0.3.82 | 14 / 11 | |
| 0.3.81 | 14 / 11 | |
| 0.3.80 | 14 / 11 | |
| 0.3.79 | 14 / 11 | |
| 0.3.78 | 14 / 11 | |
| 0.3.77 | 14 / 11 | |
| 0.3.76 | 14 / 11 | |
| 0.3.75 | 14 / 11 | |
| 0.3.74 | 14 / 11 | |
| 0.3.72 | 14 / 11 | |
| 0.3.71 | 14 / 11 | |
| 0.3.70 | 14 / 11 | |
| 0.3.69 | 14 / 11 | |
| 0.3.68 | 14 / 11 | |
| 0.3.66 | 14 / 11 | |
| 0.3.65 | 14 / 11 | |
| 0.3.64 | 14 / 11 | |
| 0.3.63 | 14 / 11 | |
| 0.3.62 | 14 / 11 | |
| 0.3.61 | 14 / 11 | |
| 0.3.60 | 14 / 11 | |
| 0.3.59 | 14 / 11 | |
| 0.3.58 | 14 / 11 | |
| 0.3.57 | 14 / 11 | |
| 0.3.56 | 14 / 11 | |
| 0.3.55 | 14 / 11 | |
| 0.3.54 | 14 / 11 | |
| 0.3.53 | 14 / 11 | |
| 0.3.52 | 14 / 11 | |
| 0.3.51 | 14 / 11 |
v0.3.106
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.105
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.101
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.100
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.99
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.98
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.97
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.96
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.95
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.94
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.93
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.92
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.91
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.90
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.89
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.88
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.87
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.86
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.85
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.84
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (devinea) than the most recent previously approved version (kranthie.sap) on 2026-03-20, but devinea is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.3.83
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (devinea) than the most recent previously approved version (kranthie.sap) on 2026-03-20, but devinea is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.3.82
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (devinea) than the most recent previously approved version (kranthie.sap) on 2026-03-17, but devinea is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.3.81
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.80
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.79
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.78
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.77
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.76
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.75
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.74
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.72
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.71
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.70
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.69
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.68
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.66
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.64
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.63
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.62
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.61
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.60
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.59
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.58
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.57
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.54
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.