runcastle@1.2.12
Burn tickets into shipped features with Claude Code.
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe automatic startup update check sends a persistent install ID, version, and platform to the package’s ping service. This is limited runtime telemetry, but the README only describes the update banner and does not disclose the ping, so it warrants a warning rather than a block.
Decision evidence
public snapshot- Server startup automatically starts the update check.
- The update ping sends a persistent install ID, package version, and platform to ping.runcastle.dev.
- The install ID is generated as a UUID and saved locally.
- The README mentions an in-app update banner but does not disclose the startup ping or its transmitted fields.
- The transmitted fields are limited to an install ID, version, and platform; no credentials or project data are sent in this request.
- The package’s documented purpose is to launch a local server and provide an in-app update banner.
Source & flagged code
8 flaggedThis package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
bin/runcastle.jsView on unpkgPackage source references child process execution.
bin/runcastle.jsView on unpkg · L1141Findings
Affected versions and remediation
This report applies to runcastle@1.2.12.
See all versions of runcastle for other recorded verdicts.
- Review the evidence and your use of runcastle@1.2.12 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.