halfcycle@0.4.11
Your coding agents are the engineers. Halfcycle is the rest of the team: product owner, architect, planner and independent reviewer for Claude Code.
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe package’s remote code checks fit its stated purpose, but it also automatically emits engagement-linked evaluation run records to a configured telemetry endpoint. Because this additional runtime telemetry is not disclosed in the README and no opt-out was identified, this merits a warning rather than a block.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A configured guard evaluation completes and the runner has both a control telemetry URL and token.
Impact
This exposes engagement-linked usage and evaluation metadata to the service without the README disclosing this additional reporting or an apparent telemetry opt-out.
Mechanism
The runner posts a run record containing engagement, phase, outcome, counts, and evaluation result to the configured telemetry endpoint.
AI rationale
The package’s remote code checks fit its stated purpose, but it also automatically emits engagement-linked evaluation run records to a configured telemetry endpoint. Because this additional runtime telemetry is not disclosed in the README and no opt-out was identified, this merits a warning rather than a block.
Evidence
bin/bin.bundle.mjsREADME.md~/.halfcycle/guard-eval-log/
Network endpoints2
guard.halfcycle.ai (default guard origin)CONTROL_TELEMETRY_URL (configured origin; no fixed host in source)
Decision evidence
public snapshotAI called this Suspicious at 87.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The runner automatically emits a run record to the configured control telemetry URL when telemetry URL and token are present.
- Run records include a service-assigned engagement ID, phase, outcome, counts, and evaluation result.
- The README documents remote guard checks and code excerpts, but does not mention the separate run-record telemetry.
Evidence against
- There are no npm lifecycle scripts; the CLI is started through the declared bin entry.
- The README says code excerpts are sent to Halfcycle for checks under the terms accepted at sign-in.
- Guard requests use a dedicated guard token and the configured guard service origin.
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
6 flaggedbin/bin.bundle.mjsView file
17608// dist/git.js
L17609: import { spawnSync } from "node:child_process";
L17610: import { existsSync, readFileSync } from "node:fs";
High
Child Process
Package source references child process execution.
bin/bin.bundle.mjsView on unpkg · L17608dist/cli.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = halfcycle@0.4.8
matchedIdentity = npm:aGFsZmN5Y2xl:0.4.8
similarity = 0.600
summary = stored previous version shares package body but lacks this dangerous source file
Critical
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/cli.jsView on unpkg5334// dist/control-origin.js
L5335: var DEFAULT_CONTROL_ORIGIN = "https://control.halfcycle.ai";
L5336: function resolveControlOrigin(env = process.env) {
L5337: const configured = env["HALFCYCLE_SERVICE_URL"]?.trim();
...
L5346: // dist/device-signin.js
L5347: import { spawn } from "node:child_process";
L5348: import { platform as platform3 } from "node:os";
Findings
1 Critical5 High3 Medium5 Low
CriticalPrevious Version Dangerous Deltadist/cli.js
HighChild Processbin/bin.bundle.mjs
HighSame File Env Network Executiondist/cli.js
HighSandbox Evasion Gated Capabilitydist/cli.js
HighCross File Remote Execution Contextdist/cli.js
HighRuntime Package Installdist/cli.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowEval
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to halfcycle@0.4.11.
See all versions of halfcycle for other recorded verdicts.
- Review the evidence and your use of halfcycle@0.4.11 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.