registry / @holostaff/cli / 0.3.7
@holostaff/cli@0.3.7
Holostaff CLI — scan, instrument, and embed copilots in your codebase
AI Security Review
scanned 4mo ago · by lpm-firewall-aiSource inspection shows a user-invoked Holostaff CLI with authenticated service calls, opt-out telemetry, and explicit repository-editing workflows. No lifecycle hook, covert exfiltration, remote code execution, broad AI-agent control-surface mutation, or persistence mechanism was found.
Static reason
No blocking static signals were detected.
Trigger
User invokes holostaff scan, deploy, login, or interactive instrumentation commands.
Impact
May upload scan artifacts to the configured Holostaff service and write user-approved project/auth state; no stealth persistence, credential harvesting, or remote payload execution found.
Mechanism
User-invoked authenticated API requests, optional telemetry, and explicit repository instrumentation.
AI rationale
Source inspection shows a user-invoked Holostaff CLI with authenticated service calls, opt-out telemetry, and explicit repository-editing workflows. No lifecycle hook, covert exfiltration, remote code execution, broad AI-agent control-surface mutation, or persistence mechanism was found.
Evidence
package.jsondist/index.jsdist/auth/credentials.jsdist/agent/runScan.jsdist/agent/uploadArtifact.jsdist/instrument/applyPlan.js~/.holostaff/credentials.json<repoRoot>/.holostaff/source.json<repoRoot> project filesos.tmpdir()/holostaff-update-check.json
Network endpoints2
holostaff-vision-1008066443043.us-central1.run.appregistry.npmjs.org/@holostaff/cli/latest
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
Evidence against
- package.json has no preinstall, install, or postinstall hook.
- dist/index.js only runs after the user invokes the holostaff CLI.
- dist/auth/credentials.js stores only its own token under ~/.holostaff with restrictive permissions.
- dist/agent uploads occur through scan flows; interactive scanning presents a confirmation step.
- dist/instrument/applyPlan.js modifies the current repository only through explicit instrumentation actions and git commands.
- dist/telemetry.js sends documented opt-out telemetry without source code, paths, or raw workspace ID.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
1 flaggeddist/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 · L1Findings
2 Medium5 Low
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.3.7.
See all versions of @holostaff/cli for other recorded verdicts.
- Review the evidence and your use of @holostaff/cli@0.3.7 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.