@ubnt/cawcut
CawCut developer CLI — auth, generate, app run, task status
This report shows the evidence for @ubnt/cawcut@0.1.5. 2 of 9 known versions are blocked or flagged. The newest version, 0.8.0, is flagged. See all versions.
AI Security Review
scanned 4mo ago · by lpm-firewall-aiThe decisive behavior is not ordinary CLI networking; it is unconsented postinstall mutation of foreign/broad AI-agent control surfaces. Under the provided policy this should be blocked even though the repo and API names appear package-aligned. 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 dist/postinstall.js.
- dist/postinstall.js runs on global install and calls installCawcutSkills without user command consent.
- dist/lib/skills-install.js spawns npx --yes skills add Ubiquiti-UID/flow-cawcut-skill -g -y --skill *.
- dist/lib/skills-agents.js targets cursor, claude-code, and codex agent skill directories.
- dist/lib/bootstrap-skills.js can also auto-install missing skills during normal CLI invocation.
- postinstall skips local installs, CI=true, or CAWCUT_SKIP_SETUP=1.
- OAuth/API endpoints in config/products.json are package-aligned cawcut.com services.
- Credential storage is local .cawcut credentials.json with 0600 mode; no source evidence of credential exfiltration.
- Uninstall path removes named CawCut skills and local credentials.
Source & flagged code
8 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/lib/uninstall-cawcut.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @ubnt/cawcut@0.1.5.
The versions list below shows the verdict for each recorded version.
- Avoid installing @ubnt/cawcut@0.1.5. 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.