@holostaff/cli@0.11.1
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 execution and network transfers belong to the user-run simulation feature: it starts the configured test app, sends observations to the selected model, and reports results to Holostaff. The manifest has no install hooks, and the reviewed source shows no unrelated credential collection or concealed automatic behavior.
Decision evidence
public snapshot- The manifest has no install lifecycle hooks; its scripts are development and build commands.
- The CLI dispatches simulation work only for the explicit `simulate` command.
- CI simulation requires a Holostaff API key and source ID before it runs.
- The CI runner uploads simulation run data to the configured Holostaff API.
- The engine sends page observations and screenshots to the selected model endpoint as part of its simulation loop.
- Simulation data, which can include page content, is sent to a model endpoint and run results are uploaded to Holostaff; this is consistent with the stated simulation feature and requires an explicit command.
Source & flagged code
7 flaggedPackage source references child process execution.
dist/instrument/openPullRequest.jsView on unpkg · L18This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/engine/run.jsView on unpkgFindings
Affected versions and remediation
This report applies to @holostaff/cli@0.11.1.
See all versions of @holostaff/cli for other recorded verdicts.
- Review the evidence and your use of @holostaff/cli@0.11.1 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.