@twing/cli@1.3.2
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe package has a real agent configuration lifecycle capability, gated to global installation or an explicit setup flag. Under the package policy, first-party agent integration setup warrants a warning, while the inspected behavior does not support a malicious block.
Decision evidence
public snapshot- package.json runs postinstall.cjs after installation.
- The postinstall hook allows machine setup for global installs or with --machine-setup; other installs exit.
- Machine setup wires Claude Code, OpenCode, and Codex hooks and records an auto-managed marker.
- Codex configuration is located under its configured home or ~/.codex.
- The package identifies a machine-global OpenCode plugin and a Claude Code settings hook.
- test-support.js describes its child-process and fetch-related code as test fixtures.
- Ordinary dependency installs do not enter machine setup.
- The observed setup is first-party CLI integration, not evidence of credential theft or an unrelated control-surface mutation.
Source & flagged code
7 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 child process execution.
dist/opencode-adapter.jsView on unpkg · L12Findings
Affected versions and remediation
This report applies to @twing/cli@1.3.2.
See all versions of @twing/cli for other recorded verdicts.
- Review the evidence and your use of @twing/cli@1.3.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.