registry / @telora/daemon / 0.22.181
@telora/daemon@0.22.181
Agent orchestration daemon for Telora - spawns and manages Claude Code instances
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe package has no npm install hook, and its agent setup is part of an explicit connector flow. Automatic npm ci during worktree provisioning can still execute project-controlled dependency scripts, leaving a concrete but product-related execution risk.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A coding worktree session starts package provisioning.
Impact
Dependency lifecycle scripts may execute code in the worktree environment without a separate prompt at install time.
Mechanism
The daemon runs npm ci in selected package directories in the worktree.
AI rationale
The package has no npm install hook, and its agent setup is part of an explicit connector flow. Automatic npm ci during worktree provisioning can still execute project-controlled dependency scripts, leaving a concrete but product-related execution risk.
Evidence
dist/spawn/worktree-session.jsdist/worktree/worktree-package-provisioning.jsdist/worktree/install-inputs.js
Decision evidence
public snapshotAI called this Suspicious at 76.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- A coding worktree session starts package provisioning in the background.
- Provisioning runs npm ci in each selected package directory, which can execute that project’s dependency lifecycle scripts.
- The manifest has no install hook; its prepublishOnly script builds and stamps the package.
Evidence against
- The agent configuration writers are part of the explicit connect/setup flow and configure Telora’s MCP integration.
- The inspected source shows no confirmed credential theft, destructive behavior, or remote payload execution.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
6 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/verification-baseline-run.js#virtual:normalized:round1View file
Findings
1 Critical4 High4 Medium5 Low
CriticalPrevious Version Dangerous Deltadist/shell/unified-shell.js
HighChild Processdist/update/self-update.js
HighShelldist/verify/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
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to @telora/daemon@0.22.181.
See all versions of @telora/daemon for other recorded verdicts.
- Review the evidence and your use of @telora/daemon@0.22.181 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.