@telora/daemon@0.24.11
⚠ Under reviewAgent orchestration daemon for Telora - spawns and manages Claude Code instances
AI Security Review
scanned 5d ago · by lpm-firewall-aiSource inspection found no confirmed attack, but the required clean review covers more files than the citation limit allows. Manual review is warranted because that coverage gap remains unresolved, not because scanner labels establish maliciousness.
Decision evidence
public snapshot- The daemon can install a newer release by default when it reaches a safe idle point; the update uses the configured release channel.
- The connect flow writes daemon and agent configuration, and I could not complete the required package-wide clean citation coverage within the citation limit.
- The manifest’s publication hooks build the package and copy shipped documentation; no install-time lifecycle hook is listed.
- The inspected updater installs the daemon’s own release from npmjs by default or an explicitly configured channel.
- The inspected agent configuration writes occur through the connect flow, and the seed writer preserves content outside its delimited block.
Source & flagged code
8 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.24.11.
See all versions of @telora/daemon for other recorded verdicts.
- Review the evidence and your use of @telora/daemon@0.24.11 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.