runcastle@1.6.2
Burn tickets into shipped features with Claude Code.
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe default server startup sends a persistent random install ID, version, and platform to the package's own update endpoint. The observed payload is limited, but the README does not disclose the identifier collection, so this is suspicious runtime telemetry.
Decision evidence
public snapshot- Starting the server automatically invokes the update check.
- The update check posts a persistent install ID, package version, and platform to ping.runcastle.dev.
- The README describes an in-app update banner but does not explain that the check sends a persistent install ID.
- The observed update payload contains no credentials, project data, or file contents.
- The code recognizes the DO_NOT_TRACK environment variable.
Source & flagged code
8 flaggedPackage source references child process execution.
bin/runcastle.jsView on unpkg · L2190Source 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.2.
See all versions of runcastle for other recorded verdicts.
- Review the evidence and your use of runcastle@1.6.2 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.