thalamus@1.5.67
⚠ Under reviewMobile and Web client for Claude Code
AI Security Review
scanned 24d ago · by lpm-firewall-aiInspected lifecycle and flagged source show package-local tool extraction and local transcript or metrics handling, without a confirmed attack chain. The archive is non-source binary data and required clean citation coverage cannot be completed, so the unresolved binary prevents a clean verdict.
Decision evidence
public snapshot- The install hook runs a package-local tool unpacker; the unpacker identifies its purpose as extracting platform-specific binaries.
- The flagged API locations derive Claude project transcript paths and parse local transcript text.
- The flagged index locations compute friction metrics from local Claude project data and write state and metrics files.
- The MCP wrapper starts the package’s own bridge with inherited standard streams and forwards termination signals.
- The shipped library and index entrypoints load package-local API and index modules.
- The supplied archive is a binary and could not be evaluated through source citations; its presence alone does not establish malicious behavior.
Source & flagged code
18 flaggedPackage defines install-time lifecycle scripts.
package.jsonView on unpkgPackage source references child process execution.
bin/thalamus-mcp.mjsView on unpkg · L2Findings
Affected versions and remediation
This report applies to thalamus@1.5.67.
See all versions of thalamus for other recorded verdicts.
- Review the evidence and your use of thalamus@1.5.67 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.