halfcycle@0.4.16
Your coding agents are the engineers. Halfcycle is the rest of the team: it scopes, designs, plans and reviews production software, and runs the build inside your own Claude Code.
AI Security Review
scanned 5d ago · by lpm-firewall-aiThis is not credential exfiltration: the engagement token authenticates to the configured Halfcycle telemetry service, and the record contains run metadata rather than raw tool input. The automatic hook telemetry has no user-facing disclosure or opt-out visible in the inspected package source, so it warrants a warning.
Decision evidence
public snapshot- Configured Claude hooks automatically emit and post a run record after a guard evaluation.
- The record is sent as JSON to the configured telemetry URL with the engagement token as bearer authorization.
- The record builder includes a random run ID, engagement ID, run type, timestamp, and outcome; it does not serialize the tool input.
- The package source inspected does not show a user-facing disclosure or telemetry opt-out for these hook records.
- The telemetry uses a configured Halfcycle service URL and engagement token, rather than sending credentials to an unrelated collector.
- The record builder describes run metadata and evaluation status, not raw prompts, commands, or credential values.
- The package exposes its CLI through an explicit command and declares no npm lifecycle hook.
Source & flagged code
10 flaggedPackage source references child process execution.
bin/bin.bundle.mjsView on unpkg · L19172Findings
Affected versions and remediation
This report applies to halfcycle@0.4.16.
See all versions of halfcycle for other recorded verdicts.
- Review the evidence and your use of halfcycle@0.4.16 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.