@rallycry/conveyor-agent@11.0.2
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-aiThe manifest has no npm install lifecycle hook, and the inspected credential changes support the package’s agent runtime. The scanner’s credential and persistence hints do not establish an unrelated credential recipient or a concrete attack.
Decision evidence
public snapshot- package.json defines prepublishOnly as tsup and has no preinstall, install, or postinstall hook.
- The boot code copies Claude credentials into a pod-local file and repoints the package’s shared Claude credential path to it; this is local agent setup.
- Claude credentials are written from environment-provided OAuth material to the Claude config directory; the inspected code does not show those credentials being sent to an unrelated endpoint.
- The flagged chunks implement package functions for git credential setup, workbench framing, and an environment-configured OOM watchdog.
- The inspected upload code sends selected workspace file bytes to a URL returned by the workbench upload request.
Source & flagged code
12 flagged · loading sourceSource appears to send environment or credential material to an external endpoint.
dist/chunk-QETNCXIR.jsView on unpkg · L129A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
dist/chunk-QETNCXIR.jsView on unpkg · L129Findings
Affected versions and remediation
This report applies to @rallycry/conveyor-agent@11.0.2.
See all versions of @rallycry/conveyor-agent for other recorded verdicts.
- Review the evidence and your use of @rallycry/conveyor-agent@11.0.2 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.