@rallycry/conveyor-agent@11.0.50
Conveyor Agent Runner v10 - PTY harness for the task chat (SDK harness for audit/project-chat). Agent-as-User architecture with BaseService patterns. Works locally too.
AI Security Review
scanned 12d ago · by lpm-firewall-aiSource inspection found no install-time attack: the package’s only lifecycle hook builds the package, and the flagged boot and agent-setting behavior is gated by container or session startup. These behaviors align with running an agent inside a configured Conveyor container, and the inspected code does not establish a concrete malicious chain.
Decision evidence
public snapshot- package.json exposes the agent and gate CLIs; its only lifecycle hook is prepublishOnly running the build tool.
- The boot path requires an explicit container role and bootstrap credentials before proceeding.
- Boot code places Claude credentials in pod-local storage and wires the container home for persistence.
- The Claude settings and hook helper are written to a temporary directory when the agent session starts.
- The optional Grimoire fetch is gated on a matching project submodule and a supplied GitHub token.
- The flagged OOM watchdog reads process and memory information for container resource management.
Source & flagged code
7 flagged · loading sourceSource writes persistence or remote-access backdoor material.
dist/boot-GD5XMLPS.jsView on unpkg · L35A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
dist/boot-GD5XMLPS.jsView on unpkg · L35Findings
Affected versions and remediation
This report applies to @rallycry/conveyor-agent@11.0.50.
See all versions of @rallycry/conveyor-agent for other recorded verdicts.
- Review the evidence and your use of @rallycry/conveyor-agent@11.0.50 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.