runcastle@1.6.1
Burn tickets into shipped features with Claude Code.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe package performs an automatic update ping that includes a persistent installation identifier, and the README does not disclose this runtime telemetry. The collected fields are limited and the ping has a DO_NOT_TRACK bypass, so this warrants a warning rather than a block.
Decision evidence
public snapshot- Server startup calls the update check automatically.
- The check POSTs an install ID, package version, and platform to the package’s ping endpoint.
- The install ID is a random UUID persisted under the package data directory.
- The ping sends only an install ID, version, and platform; no credentials or project data appear in its request body.
- The ping can be bypassed with DO_NOT_TRACK.
Source & flagged code
8 flaggedPackage source references child process execution.
bin/runcastle.jsView on unpkg · L2164Source combines command execution, command-output handling, and outbound requests; review data flow before blocking.
Findings
Affected versions and remediation
This report applies to runcastle@1.6.1.
See all versions of runcastle for other recorded verdicts.
- Review the evidence and your use of runcastle@1.6.1 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.