thalamus@1.5.10
Mobile and Web client for Claude Code
AI Security Review
scanned 1mo ago · by lpm-firewall-aiInstall-time code unpacks and chmod's opaque native archives, and the required arm64 Linux archive has no readable source text, so the extracted payload stays unverified. Readable Claude session and OAuth paths are user-started and bound to the Anthropic usage API, which does not clear that install payload.
Decision evidence
public snapshot- package.json postinstall runs node scripts/unpack-tools.cjs during npm install.
- unpack-tools.cjs gunzips the platform difftastic and ripgrep tar.gz archives into tools/unpacked and chmod 755 on every non-.node file.
- tools/archives/difftastic-arm64-linux.tar.gz is non-UTF8; it has no printable excerpt, so the install-time extracted executables cannot be verified.
- The .claude projects path only checks whether a session jsonl file exists when a session is resumed.
- The daemon reads the local Claude OAuth access token and sends it only to https://api.anthropic.com/api/oauth/usage; stored quota fields omit that token.
- bin/thalamus-mcp.mjs spawns the local dist MCP bridge with the current Node binary.
- dist/lib.cjs and dist/lib.mjs only re-export the API client, and package.json does not depend on its own name.
Source & flagged code
14 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.10.
See all versions of thalamus for other recorded verdicts.
- Review the evidence and your use of thalamus@1.5.10 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.