@telora/daemon@0.21.198
Agent orchestration daemon for Telora - spawns and manages Claude Code instances
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe scanner's execution and shell signals correspond to product functions, and the manifest has no install hook. I classify the first-party agent configuration and automatic settings refresh as a warning-level extension lifecycle capability; the inspected source does not support blocking the package.
Decision evidence
public snapshot- The Claude, Codex, Cline, Cursor, and VS Code setup writes agent or MCP configuration, including files that agent clients load.
- Daemon startup refreshes configured products' Claude settings, and those settings include a SessionStart hook that runs telora-daemon session-state.
- The manifest's prepublishOnly script builds and stamps metadata; it is not an install lifecycle hook.
- The connect flow performs the setup and starts the daemon; the inspected configuration writes are part of this explicit product setup.
- The hook invokes the package's own daemon command, and the inspected runtime-operation hints concern merge resolution and installing a configured sidecar.
Source & flagged code
6 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.21.198.
See all versions of @telora/daemon for other recorded verdicts.
- Review the evidence and your use of @telora/daemon@0.21.198 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.