psyclaw@0.29.18
A standalone, evidence-grounded social-science research agent with research contracts, evidence gates, and recoverable workflows
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package contains meaningful user-invoked agent-control and telemetry capabilities, so it warrants a warning. Source inspection found no install hook, self-dependency chain, hidden payload, or concrete malicious behavior.
Decision evidence
public snapshot- The launch path replaces the underlying agent identity and enables file-write and shell tools.
- Telemetry is enabled by default and sends CLI events to vendor telemetry services.
- The local panel can execute catalog-derived shell commands after a request-provided approval flag.
- The panel writes settings in the agent runtime directory.
- MCP can launch configured child processes, although it uses an empty environment and disables shell execution.
- The scanner-marked Python file is a normal pytest fixture, not an embedded payload.
- package.json has only a prepublish-only hook, not an install lifecycle hook.
- No self-dependency on psyclaw was found.
- The TUI requires an explicit Y confirmation before agent installation or skill import.
- The MCP transport clears inherited environment variables and uses shell false.
- No credential harvesting, opaque payload loading, destructive action, or reviewer-directed package text was found.
- The bundled test fixture only defines local test helpers.
Source & flagged code
7 flaggedPackage source references dynamic require/import behavior.
dist/apps/panel/observability.jsView on unpkg · L38Findings
Affected versions and remediation
This report applies to psyclaw@0.29.18.
See all versions of psyclaw for other recorded verdicts.
- Review the evidence and your use of psyclaw@0.29.18 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.