runcastle@1.4.1
Burn tickets into shipped features with Claude Code.
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe reported credential redirection is not present in the reviewed auth path: credentials are selected by runtime and passed to the matching agent. The default update check sends a persistent install ID, version, and platform to the vendor ping endpoint, while the README mentions update notices but does not disclose this telemetry, so this warrants a warning.
Decision evidence
public snapshot- The update check POST sends a persistent install ID, package version, and platform.
- The telemetry goes to https://ping.runcastle.dev/ping and is used by the app’s update check.
- Setting DO_NOT_TRACK skips the ping and checks npm for the latest version instead.
- Runtime credentials are read using the selected service’s key and passed to that agent runtime.
- The manifest declares a CLI binary and no lifecycle install script.
- The observed ping contains no credentials, project contents, or machine-specific details beyond platform.
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 · L1295Findings
Affected versions and remediation
This report applies to runcastle@1.4.1.
See all versions of runcastle for other recorded verdicts.
- Review the evidence and your use of runcastle@1.4.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.