@telora/daemon@0.22.72
Agent orchestration daemon for Telora - spawns and manages Claude Code instances
AI Security Review
scanned 1mo ago · by lpm-firewall-aiNo malicious npm lifecycle chain or secret-exfiltration behavior was found. The package nevertheless has explicit persistent agent-extension and sidecar-execution capabilities that warrant a warning.
Decision evidence
public snapshot- The explicit connect command registers a Telora MCP server in the operator's personal Codex configuration.
- The connect flow can merge Telora tracking hooks into the user's Claude settings when a companion executable is present.
- The daemon can fetch a configured Git source, install it into a virtual environment, and launch it as a sidecar.
- The package has no npm install lifecycle hook; its only lifecycle script is prepublishOnly.
- The configuration and hook writes occur only after the user invokes the connect command.
- The observed network request redeems a user-supplied connect token against the Telora service.
- No source evidence showed credential harvesting, secret exfiltration, hidden install-time execution, or self-dependency.
Source & flagged code
7 flagged · loading sourcePackage source references child process execution.
dist/update/self-update.jsView on unpkg · L25Package source invokes a package manager install command at runtime.
dist/update/self-update.jsView on unpkg · L16Findings
Affected versions and remediation
This report applies to @telora/daemon@0.22.72.
See all versions of @telora/daemon for other recorded verdicts.
- Review the evidence and your use of @telora/daemon@0.22.72 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.