cielara-enterprise
Cielara Enterprise MCP connector — installs an MCP server for Claude, Codex, and Cursor that connects to the Cielara knowledge graph, agent memory, and world model, plus the code-graph sidecar, skills, and grep enrichment hooks.
This report shows the evidence for cielara-enterprise@0.1.41. 1 of 3 known versions is blocked or flagged. The newest version, 0.1.43, is flagged. See all versions.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiSource confirms an unconsented npm postinstall mutation of broad foreign AI-agent control surfaces. This meets the blocking install-control-surface policy independently of the telemetry concern.
Decision evidence
public snapshot- package.json runs postinstall automatically.
- scripts/postinstall.js calls install() on interactive installs.
- lib/install.js writes MCP entries to Codex, Claude Code, and Cursor configs by default.
- Installed MCP command invokes `npx -y cielara-enterprise mcp`.
- lib/telemetry.js sends device and usage fields to https://cielaracode.com/v1/telemetry by default.
- skills/cielara-usage/SKILL.md instructs agents to flush telemetry with elevated permissions.
- preinstall only guards conflicting global sibling installs.
- postinstall skips its integration setup in CI.
- Telemetry requires buffered events and authenticated credentials to transmit.
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 unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to cielara-enterprise@0.1.41.
The versions list below shows the verdict for each recorded version.
- Avoid installing cielara-enterprise@0.1.41. 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.