@telora/daemon@0.22.144
⚠ Under reviewAgent orchestration daemon for Telora - spawns and manages Claude Code instances
AI Security Review
scanned 3d ago · by lpm-firewall-aiInspected source supports normal daemon self-update and explicit integration setup, and the manifest has no install hook. A clean verdict would require citations across the extensive required path set, so the review remains unresolved rather than relying on scanner labels.
Decision evidence
public snapshot- The manifest exposes a CLI and import entrypoint, with only a prepublishOnly build hook; it has no install lifecycle hook.
- The daemon starts automatic updates when enabled, using a cached candidate version and an idle gate; this is package self-update behavior.
- The connect command writes daemon configuration and agent setup files as part of its documented user-invoked setup flow.
- Inspected update commands use fixed git/npm arguments and update the daemon’s own installation; the inspected sources show no unrelated credential transfer or consumer policy mutation.
- The connect path describes setup initiated by `telora-daemon connect <token>` and writes configuration under the user’s selected repository or agent configuration locations.
Source & flagged code
6 flagged · loading sourcePackage source references child process execution.
dist/update/self-update.jsView on unpkg · L27Package source invokes a package manager install command at runtime.
dist/update/self-update.jsView on unpkg · L17Findings
Affected versions and remediation
This report applies to @telora/daemon@0.22.144.
See all versions of @telora/daemon for other recorded verdicts.
- Review the evidence and your use of @telora/daemon@0.22.144 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.