@oxgeneral/orch
AI agent runtime — orchestrate Claude, Cursor, Codex & OpenCode as one team. Multi-agent task automation with state machine, auto-retry, inter-agent messaging, goals and teams. Zero-config CLI + programmatic API.
This report shows the evidence for @oxgeneral/orch@1.0.27. 2 of 2 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 4mo ago · by lpm-firewall-aiStatic source inspection confirms lifecycle-triggered writes into ~/.claude/skills, a foreign/broad AI-agent control surface covered by the block policy. The absence of network exfiltration does not remove the unconsented install-time agent control mutation.
Decision evidence
public snapshot- package.json runs postinstall: node scripts/postinstall.cjs || true
- scripts/postinstall.cjs writes package skill to ~/.claude/skills/orch/SKILL.md during npm install
- scripts/postinstall.cjs mutates dependency files under node_modules/ink/build at install time
- skills/orch/SKILL.md is packaged agent-facing instruction content for Claude Code
- No network calls or endpoint use in scripts/postinstall.cjs
- Postinstall catches errors and only shows banner in interactive stderr
- Main package purpose is AI-agent orchestration with Claude/Codex/Cursor/OpenCode bins
- No credential harvesting or exfiltration found in inspected install script
Source & flagged code
6 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.
dist/chunk-6DWHQPTE.jsView on unpkg · L9Findings
Affected versions and remediation
This report applies to @oxgeneral/orch@1.0.27.
The versions list below shows the verdict for each recorded version.
- Avoid installing @oxgeneral/orch@1.0.27. 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.