@coaligne/cli
This report shows the evidence for @coaligne/cli@0.0.5, the only known version.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiSource confirms the scanner finding: this is an unconsented postinstall chain that modifies multiple foreign AI-agent configurations and establishes persistence. That meets the firewall block boundary regardless of the package's stated collaboration purpose.
Decision evidence
public snapshot- package.json postinstall silently invokes daemon, skill, and MCP installation.
- dist/chunk-Y26Y325W.js installs bundled skills into Codex, Gemini, Claude, and WorkBuddy directories.
- dist/chunk-2FTAEUOQ.js writes a coAligne MCP server into five agent configuration files.
- dist/chunk-BDZMRU7C.js installs a persistent macOS LaunchAgent with KeepAlive.
- MCP configuration targets https://app.coaligne.com/mcp and can retain an access token in config.
- No eval, VM, dynamic remote-code loader, or credential-harvesting routine found.
- Cloud sync excludes common secret-file patterns by default.
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 unpkgFindings
Affected versions and remediation
This report applies to @coaligne/cli@0.0.5.
The versions list below shows the verdict for each recorded version.
- Avoid installing @coaligne/cli@0.0.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.