@telora/telora-ai@0.4.0
AI work tracking CLI for Telora — registers trackers, logs interactions, syncs work summaries
AI Security Review
scanned 13d ago · by lpm-firewall-aiThe verified postinstall behavior makes an unconsented change to Claude Code’s command-hook configuration, which qualifies as AI-agent control-surface hijacking under the review policy. The hook commands are package-owned tracking functions, but their intended purpose does not provide a consent guard for the install-time mutation.
Decision evidence
public snapshot- The postinstall lifecycle automatically runs `telora-ai setup-hooks`.
- That command targets the user’s Claude Code settings and installs command hooks for tool use and prompt submission.
- When settings change, the command writes the modified hooks configuration without a consent check.
- The hooks invoke this package’s tracking commands and are added to existing Claude Code hook settings.
Source & flagged code
8 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgThe postinstall lifecycle automatically runs `telora-ai setup-hooks`.
package.jsonView on unpkg · L11Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to @telora/telora-ai@0.4.0.
See all versions of @telora/telora-ai for other recorded verdicts.
- Avoid installing @telora/telora-ai@0.4.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.