@holostaff/cli@0.10.3
Scan your repo, map your workflows, and create workflow autopilots your users can hand a task to.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe flagged command requires an explicit simulation invocation and uses credentials with the intended Holostaff or configured model service. Its process execution and result uploads support the package’s simulation purpose, with no reviewed evidence of unrelated data collection or transmission.
Decision evidence
public snapshot- The package exposes `dist/index.js` as its CLI entry point.
- The simulation runner is reached through the explicit `holostaff simulate` command and uses its CI mode only when `--ci` is set.
- CI simulation requires a Holostaff API key and sends it to the configured API base, which defaults to Holostaff’s service.
- The engine sends model requests to the configured OpenAI-compatible endpoint, defaulting to `api.openai.com`, using the configured model key.
- The runner uploads simulation results to the Holostaff API as part of the requested simulation workflow.
- CI simulation can execute service commands from the repository’s `.holostaff/environment.json` recipe and access configured CI credentials; these actions occur as part of the explicitly invoked simulation feature.
Source & flagged code
6 flaggedPackage source references child process execution.
dist/instrument/openPullRequest.jsView on unpkg · L18Package source references weak cryptographic algorithms.
dist/deploy/editsKey.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @holostaff/cli@0.10.3.
See all versions of @holostaff/cli for other recorded verdicts.
- Review the evidence and your use of @holostaff/cli@0.10.3 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.