@intutic/cli@2.9.0
Intutic CLI — sync daemon, harness detection, and workspace management
AI Security Review
scanned 19d ago · by lpm-firewall-aiThe package manifest has a CLI entry point but no npm lifecycle hook. Inspected credential handling, agent configuration, skill reporting, integrity operations, and daemon installation align with explicit Intutic CLI workflows, with no confirmed attack behavior.
Decision evidence
public snapshot- The manifest defines a CLI entry point and contains no preinstall, install, or postinstall hook.
- Agent configuration is written through the explicit `intutic connect` workflow; the inspected adapter files describe workspace rules and hooks for supported agents.
- The daemon installer exposes an explicit install operation, and the package has no lifecycle hook that invokes it during npm installation.
- Stored credentials are retrieved from the OS keychain or local credential store and are passed to API clients for the configured control plane.
- Skill reports and integrity operations use the authenticated Intutic API for their corresponding workspace operations.
- No inspected source establishes an unconsented credential transfer, destructive action, or automatic foreign agent configuration mutation.
Source & flagged code
7 flaggedPackage source references weak cryptographic algorithms.
dist/commands/rollback.jsView on unpkg · L29Source writes installer persistence such as shell profile or service configuration.
Findings
Affected versions and remediation
This report applies to @intutic/cli@2.9.0.
See all versions of @intutic/cli for other recorded verdicts.
- Review the evidence and your use of @intutic/cli@2.9.0 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.