registry / @telora/daemon / 0.23.0
@telora/daemon@0.23.0
⚠ Under reviewAgent orchestration daemon for Telora - spawns and manages Claude Code instances
AI Security Review
scanned 15d ago · by lpm-firewall-aiInspected source shows explicit connect setup and a publish-time build hook, with no concrete attack behavior established. The required clean review needs 12 distinct citations, but the output permits at most 8, so the result is manual review under the citation coverage rule.
Static reason
One or more suspicious static signals were detected.
Trigger
User-invoked connect flow; the package's prepublishOnly hook runs during publishing.
Impact
The inspected behavior supports ordinary package setup and publishing; no malicious effect was established.
Mechanism
Connect writes Telora daemon configuration and merges harness-specific scaffolding; prepublishOnly builds the package.
AI rationale
Inspected source shows explicit connect setup and a publish-time build hook, with no concrete attack behavior established. The required clean review needs 12 distinct citations, but the output permits at most 8, so the result is manual review under the citation coverage rule.
Evidence
package.jsondist/cli/connect.jsdist/cli/connect/agents.jsdist/cli/connect/claude.jsdist/cli/connect/config-write.jsdist/update/self-update.js
Decision evidence
public snapshotAI called this Manual Review at 68.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The manifest has a prepublishOnly build hook and no preinstall, install, or postinstall hook.
- Agent scaffolding is written by the runConnect flow when the user invokes connect.
- The connect flow registers Telora with selected agent harnesses and merges configuration.
- The daemon config stores Telora connection details in the user's home directory.
- The update code describes a global install of the Telora daemon from its update channel.
- The inspected source does not establish a concrete attack; clean citation coverage requires 12 distinct paths, exceeding the 8-citation limit.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
7 flagged · loading sourcedist/update/self-update.jsView file
27*/
L28: import { execFileSync, execFile } from 'node:child_process';
L29: import { existsSync, readFileSync, writeFileSync, mkdirSync, rmSync } from 'node:fs';
High
Child Process
Package source references child process execution.
dist/update/self-update.jsView on unpkg · L2717* Three installation modes:
L18: * - **npm**: Installed globally via `npm install -g @telora/daemon`.
L19: * Updates via `npm install -g --@telora:registry=<channel> @telora/daemon@latest`
...
L27: */
L28: import { execFileSync, execFile } from 'node:child_process';
L29: import { existsSync, readFileSync, writeFileSync, mkdirSync, rmSync } from 'node:fs';
High
Runtime Package Install
Package source invokes a package manager install command at runtime.
dist/update/self-update.jsView on unpkg · L17dist/verify/attribution/verification-baseline-run.js#virtual:normalized:round1View file
Findings
1 Critical4 High4 Medium6 Low
CriticalKnown Malicious Dependency Insertionpackage.json
HighChild Processdist/update/self-update.js
HighShelldist/verify/attribution/verification-baseline-run.js#virtual:normalized:round1
HighRuntime Package Installdist/update/self-update.js
HighSemantic Analysis Limiteddist/audit/audit-phase.js#virtual:normalized:round1
MediumNetwork
MediumEnvironment Vars
MediumShips Build Helperscripts/telora-daemon-wrapper.sh
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowWeak Cryptodist/completion/team-progress/team-progress-measure.js
Affected versions and remediation
This report applies to @telora/daemon@0.23.0.
See all versions of @telora/daemon for other recorded verdicts.
- Review the evidence and your use of @telora/daemon@0.23.0 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.