registry / @threadlines/server / 0.7.0
@threadlines/server@0.7.0
Threadlines server and CLI for running coding-agent sessions.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe inspected entrypoint and new NodePTY module perform behavior expected of a coding-agent server and CLI. The scanner’s Unicode warning was not confirmed by searches for common bidi controls, and no malicious behavior was established.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
The launcher runs when the threadlines command is invoked; PTY support is used when the server starts a configured terminal process.
Impact
No malicious data collection, credential forwarding, or unrelated execution behavior was established in the inspected sources.
Mechanism
The launcher loads the server bundle, which provides CLI/server behavior and a node-pty adapter for configured shell processes.
AI rationale
The inspected entrypoint and new NodePTY module perform behavior expected of a coding-agent server and CLI. The scanner’s Unicode warning was not confirmed by searches for common bidi controls, and no malicious behavior was established.
Decision evidence
public snapshotAI called this Clean at 78.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest describes a server and CLI for running coding-agent sessions.
- The launcher checks the supported Node version, applies command lookup handling, enables the server compile cache, then loads the CLI.
- The Node PTY adapter imports node-pty and uses it to spawn the configured shell with the supplied working directory and environment.
- The server defines a content policy that restricts page requests to listed CDNs and blocks remote images and frames.
Evidence against
- No lifecycle scripts are declared in the manifest.
- The flagged NodePTY file implements terminal process support consistent with the package’s stated purpose.
- Searches for several common bidi control characters in the flagged frontend file found no matches.
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystemNetworkShellWebSocket
HighEntropyStrings
Source & flagged code
5 flaggeddist/client/assets/SourceControlPanel-DjThTooA.jsView file
27contains invisible/control Unicode U+200E (left-to-right mark)
`,sF=HP?`\xA0`:aF,cF=`֑-߿יִ-﷽ﹰ-ﻼ`,lF=`A-Za-zÀ-ÖØ-öø-ʸ̀-ࠀ-<U+200E>Ⰰ-︀--`;RegExp(`^[^`+lF+`]*[`+cF+`]`),RegExp(`^[^`+cF+`]*[`+lF+`]`);var uF={bold:1,capitalize:1024,code:16,highlight:128,italic:2,lowercase:256,strikethrough:4,subscript:3
Critical
Trojan Source Unicode
Source contains bidi control or invisible Unicode characters associated with Trojan Source attacks.
dist/client/assets/SourceControlPanel-DjThTooA.jsView on unpkg · L27•stage = ast_semantic_analysis; reason = ast_path_work_budget_exceeded; limitedFiles = 1
High
Semantic Analysis Limited
A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
dist/client/assets/SourceControlPanel-DjThTooA.jsView on unpkgdist/bin-B1v7SPzF.mjsView file
Findings
1 Critical2 High5 Medium4 Low
CriticalTrojan Source Unicodedist/client/assets/SourceControlPanel-DjThTooA.js
HighSemantic Analysis Limiteddist/client/assets/SourceControlPanel-DjThTooA.js
HighPrevious Version Dangerous Deltadist/NodePTY-BMCTEzhZ.mjs
MediumNetwork
MediumEnvironment Vars
MediumOversized Source Filedist/bin-B1v7SPzF.mjs
MediumOversized Cli Entrypointdist/bin-B1v7SPzF.mjs
MediumStructural Risk Force Deep Review
LowEval
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @threadlines/server@0.7.0.
See all versions of @threadlines/server for other recorded verdicts.
- Review the evidence and your use of @threadlines/server@0.7.0 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.