@culvii/cli@0.0.8
Culvii CLI
AI Security Review
scanned 4d ago · by lpm-firewall-aiThis is suspicious because runtime analytics are enabled by default without disclosure in the package documentation, and unhandled-error events include the command line. I found no install-time attack or evidence that credentials are sent to an unrelated host.
Decision evidence
public snapshot- Segment analytics is enabled by default unless CULVII_TELEMETRY is set to "false".
- Tracked events can include the configured user ID and tenant ID.
- The CLI sends its full command-line arguments with unhandled-error events.
- The package documentation does not disclose this runtime telemetry.
- The package has no install, preinstall, or postinstall hook.
- The login flow exchanges OAuth tokens with Culvii’s configured authentication service.
- The child process imports local project files for the explicit development workflow.
Source & flagged code
6 flaggedThis package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/index.jsView on unpkgFindings
Affected versions and remediation
This report applies to @culvii/cli@0.0.8.
See all versions of @culvii/cli for other recorded verdicts.
- Review the evidence and your use of @culvii/cli@0.0.8 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.