registry / @holostaff/cli / 0.9.4
@holostaff/cli@0.9.4
Holostaff CLI — scan, instrument, and embed copilots in your codebase
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe package has no install hook, and the flagged runner requires an explicit `simulate --ci` invocation. It sends simulation data to the package's service and uses the model key with the configured model endpoint, consistent with the CLI's stated purpose.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user runs holostaff simulate --ci.
Impact
Simulation results and recordings are sent to the configured Holostaff service; no unrelated credential collection or covert data transfer was identified.
Mechanism
The runner retrieves scenarios using the Holostaff API key, executes configured local simulation steps, calls an OpenAI-compatible model endpoint, and uploads simulation results to the workspace service.
AI rationale
The package has no install hook, and the flagged runner requires an explicit `simulate --ci` invocation. It sends simulation data to the package's service and uses the model key with the configured model endpoint, consistent with the CLI's stated purpose.
Evidence
.holostaff/environment.json.holostaff/simulate.json.holostaff/sim-runsscripts/sim/runsopts.report
Network endpoints3
holostaff-vision-1008066443043.us-central1.run.appapi.openai.comwww.holostaff.ai
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package manifest has no preinstall, install, or postinstall script.
- The CI simulation runner is invoked only through the CLI's explicit simulate command.
- CI mode requires HOLOSTAFF_API_KEY and uses it to fetch simulation data from the configured Holostaff API.
- Run results and optional recordings are uploaded to the Holostaff simulation API as part of the simulation workflow.
- The engine uses an OpenAI key with api.openai.com by default, or a configured OpenAI-compatible model endpoint.
Evidence against
- The runner executes configured recipe commands and starts services; this behavior is confined to an explicitly invoked CI simulation.
- The workflow writes simulation artifacts under .holostaff/sim-runs and may write a report to the user-specified path.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
6 flaggeddist/instrument/openPullRequest.jsView file
18*/
L19: import { execFile } from 'node:child_process';
L20: import { promisify } from 'node:util';
High
Child Process
Package source references child process execution.
dist/instrument/openPullRequest.jsView on unpkg · L18dist/deploy/editsKey.jsView file
1/**
L2: * Stable SHA-1 hash of customerEdits — pair for the server's
Low
Weak Crypto
Package source references weak cryptographic algorithms.
dist/deploy/editsKey.jsView on unpkg · L1dist/commands/simulateCiRunner.jsView file
•
Findings
1 Critical4 High2 Medium5 Low
CriticalPrevious Version Dangerous Deltadist/commands/simulateCiRunner.js
HighChild Processdist/instrument/openPullRequest.js
HighCommand Output Exfiltrationdist/commands/simulateCiRunner.js
HighTrigger Reachable Command Output Exfiltrationdist/commands/simulateCiRunner.js
HighSemantic Analysis Limiteddist/engine/run.js#virtual:normalized:round1
MediumNetwork
MediumEnvironment Vars
LowScripts Present
LowWeak Cryptodist/deploy/editsKey.js
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @holostaff/cli@0.9.4.
See all versions of @holostaff/cli for other recorded verdicts.
- Review the evidence and your use of @holostaff/cli@0.9.4 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.