swe-pro-agents
49 specialized OpenCode subagent profiles + 7 delivery pipeline skills — SWE roles, research, architecture, and code analysis agents
This report shows the evidence for swe-pro-agents@1.2.0. 1 of 8 known versions is blocked or flagged. The newest version, 3.0.1, is flagged. See all versions.
AI Security Review
scanned 4mo ago · by lpm-firewall-aiSource inspection confirms automatic postinstall writes to OpenCode agent/skill locations, including broad unprefixed skill names, without a separate user setup command. The content is mostly benign and package-aligned, but the lifecycle mutation itself crosses the firewall block boundary for AI-agent control surfaces. Product guard normalized a concrete AI-agent control hijack publish_block to the blockable dangerous-capability shape.
Decision evidence
public snapshot- package.json runs postinstall: node scripts/install.js.
- scripts/install.js automatically copies agents to ~/.config/opencode/agents/swe-pro-agents/.
- scripts/install.js automatically copies unprefixed skills into shared ~/.config/opencode/skills/.
- Skill names like reviewer, testing, planner, repository are generic and may overwrite/control broad OpenCode behavior.
- preuninstall removes only ~/.config/opencode/agents/swe-pro-agents, leaving copied skills behind.
- No package code found for credential harvesting, exfiltration, eval/vm, child_process, or runtime network calls.
- CLI only prints setup/status/version/help and reads opencode.json for status.
- Agent/skill prompts appear package-aligned software-engineering roles, not covert data theft instructions.
Source & flagged code
4 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgPackage source references dynamic require/import behavior.
bin/swe-pro-agents.jsView on unpkg · L12Findings
Affected versions and remediation
This report applies to swe-pro-agents@1.2.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing swe-pro-agents@1.2.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.