halfcycle@0.3.25
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 28d ago · by lpm-firewall-aiThe package provides explicit CLI setup that writes Claude Code settings and hooks, so it has a concrete agent-configuration capability. The manifest has no install lifecycle hook and the installer uses an allowlist, supporting a warning rather than a block.
Static reason
No blocking static signals were detected.
Trigger
A user runs the halfcycle CLI install command or its bare form.
Impact
The installed hooks and settings can influence later Claude Code sessions in the target repository.
Mechanism
The installer writes to an allowlisted set of Claude configuration and Halfcycle paths, including Claude settings and hooks.
AI rationale
The package provides explicit CLI setup that writes Claude Code settings and hooks, so it has a concrete agent-configuration capability. The manifest has no install lifecycle hook and the installer uses an allowlist, supporting a warning rather than a block.
Evidence
dist/bin.jsdist/index.jsdist/engagement-credential.d.tsbin/bin.bundle.mjspackage.json
Network endpoints2
control.halfcycle.aiguard.halfcycle.ai
Decision evidence
public snapshotAI called this Suspicious at 87.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The manifest exposes a CLI and has no npm lifecycle hook; setup runs through the CLI.
- The CLI installer limits writes to listed Claude configuration and Halfcycle paths.
- The installer command can set up the target repository, and its installer writes Claude settings and hooks.
- The credential declaration describes a hook sourcing a per-engagement environment file.
- The bundled guard binary is a package entrypoint used by the installer.
- The CLI sends device sign-in requests to the configured Halfcycle service.
Evidence against
- The setup is activated by running the CLI, not by npm installation.
- The installer has a write allowlist, and the sign-in request targets the configured Halfcycle service.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
6 flaggedbin/bin.bundle.mjsView file
15437// dist/git.js
L15438: import { spawnSync } from "node:child_process";
L15439: import { readFileSync } from "node:fs";
High
Child Process
Package source references child process execution.
bin/bin.bundle.mjsView on unpkg · L15437dist/bin.jsView file
1841var MCP_HEADERS_HELPER_REL = ".halfcycle/mcp-headers.sh";
L1842: var MCP_HEADERS_HELPER_COMMAND = `/bin/sh -c 'd=$(pwd); while [ ! -f "$d/${MCP_HEADERS_HELPER_REL}" ] && [ "$d" != / ]; do d=$(dirname "$d"); done; [ -f "$d/${MCP_HEADERS_HELPER_RE...
L1843: var GENERATED_MCP_HEADERS_HEADER = "# Halfcycle MCP connection headers \u2014 generated by";
High
2287// dist/control-origin.js
L2288: var DEFAULT_CONTROL_ORIGIN = "https://control.halfcycle.ai";
L2289: function resolveControlOrigin(env = process.env) {
L2290: const configured = env["HALFCYCLE_SERVICE_URL"]?.trim();
...
L2299: // dist/device-signin.js
L2300: import { spawn } from "node:child_process";
L2301: import { platform as platform3 } from "node:os";
Findings
4 High4 Medium4 Low
HighChild Processbin/bin.bundle.mjs
HighShelldist/bin.js
HighSame File Env Network Executiondist/bin.js
HighTrigger Reachable External Post Callbackdist/bin.js
MediumNetwork
MediumEnvironment Vars
MediumSuspicious Lifecycle Evidencepackage.json
MediumAi Review Evidencedist/bin.js
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to halfcycle@0.3.25.
See all versions of halfcycle for other recorded verdicts.
- Review the evidence and your use of halfcycle@0.3.25 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.