@sap-ux/abap-deploy-config-sub-generator@1.0.75
Sub generator for ABAP deployment configuration
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the generator's project writes and dependency installation occur during its normal Yeoman workflow. It sends telemetry after configuration generation, but the inspected source shows no unrelated endpoint or concrete malicious data flow.
Decision evidence
public snapshot- The manifest points to a Yeoman generator entry point and lists no install, preinstall, or postinstall hook.
- The generator writes deployment configuration from project settings and user answers, and stops when aborted or overwrite is declined.
- The npm install command runs in the generator's install phase, with a skipInstall option.
- Telemetry is sent after deployment configuration is added through the shared telemetry helper.
- The generator sends runtime telemetry; the inspected source does not show the shared helper's transport or the full telemetry payload.
- The package can install project dependencies when the generator runs.
Source & flagged code
5 flaggedThe manifest points to a Yeoman generator entry point and lists no install, preinstall, or postinstall hook.
package.jsonView on unpkg · L10The manifest points to a Yeoman generator entry point and lists no install, preinstall, or postinstall hook.
package.jsonView on unpkg · L52Findings
Affected versions and remediation
This report applies to @sap-ux/abap-deploy-config-sub-generator@1.0.75.
See all versions of @sap-ux/abap-deploy-config-sub-generator for other recorded verdicts.
- Review the evidence and your use of @sap-ux/abap-deploy-config-sub-generator@1.0.75 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.