runcastle@1.3.6
Burn tickets into shipped features with Claude Code.
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe server automatically sends a persistent install ID, version, and platform to the package's ping endpoint. Although DO_NOT_TRACK opts out and the README mentions update notifications, it does not disclose the telemetry payload, warranting a warning rather than a block.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
When the user starts the server.
Impact
The endpoint can track installations across server starts; the README does not explain this data collection.
Mechanism
The update check sends a persistent install ID, version, and platform to the package's ping endpoint. Setting DO_NOT_TRACK disables that ping.
AI rationale
The server automatically sends a persistent install ID, version, and platform to the package's ping endpoint. Although DO_NOT_TRACK opts out and the README mentions update notifications, it does not disclose the telemetry payload, warranting a warning rather than a block.
Evidence
bin/runcastle.jsREADME.md~/.runcastle/install-id
Network endpoints1
ping.runcastle.dev/ping
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- Starting the server automatically calls the update check.
- The check posts a persistent install ID, package version, and platform to ping.runcastle.dev.
- DO_NOT_TRACK disables the ping, but the README only describes an update banner and does not disclose the transmitted install ID or platform.
Evidence against
- The ping payload contains only an install ID, version, and platform; no credentials or project data are sent in this request.
- The manifest has no lifecycle scripts; the network call occurs when the user starts the server.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShellWebSocket
HighEntropyStringsMinifiedPossibleObfuscationUrlStrings
Source & flagged code
8 flaggedbin/runcastle.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = runcastle@1.2.11
matchedIdentity = npm:cnVuY2FzdGxl:1.2.11
similarity = 0.600
summary = stored previous version shares package body but lacks this dangerous source file
Critical
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
bin/runcastle.jsView on unpkg1197// src/pty/kill-tree.ts
L1198: import { spawn } from "child_process";
L1199: function taskkillTree(pid) {
High
Child Process
Package source references child process execution.
bin/runcastle.jsView on unpkg · L11971129if (/\.(cmd|bat)$/i.test(resolved)) {
L1130: return { file: process.env.ComSpec ?? "cmd.exe", args: ["/c", resolved, ...args] };
L1131: }
High
Findings
1 Critical5 High4 Medium4 Low
CriticalPrevious Version Dangerous Deltabin/runcastle.js
HighChild Processbin/runcastle.js
HighShellbin/runcastle.js
HighSame File Env Network Executionbin/runcastle.js
HighCredential Redirect Persistenceindex.js
HighCross File Remote Execution Contextbin/runcastle.js
MediumDynamic Requirepty-host.cjs
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowWeak Cryptobin/runcastle.js
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to runcastle@1.3.6.
See all versions of runcastle for other recorded verdicts.
- Review the evidence and your use of runcastle@1.3.6 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.