@intutic/cli@1.10.1
Intutic CLI — sync daemon, harness detection, and workspace management
AI Security Review
scanned 19d ago · by lpm-firewall-aiThe manifest has no npm lifecycle hook, and the reviewed network and agent integration paths are associated with user-invoked CLI operations or workspace settings. Scanner signals for networking, credentials, and persistence are consistent with the CLI’s stated sync and governance functions; no concrete attack behavior was found.
Decision evidence
public snapshot- package.json defines a CLI entry point and contains no install lifecycle hook.
- Skill commands inspect workspace skill and agent files; credentialed reports use the configured Intutic API client, and the audit’s destructive and content-analysis options default off unless workspace settings enable them.
- Credential helpers retrieve tokens from the operating system keychain or credentials store; reviewed callers use the Intutic API client or package-owned harness setup functions.
- Harness adapter locations identify workspace or user configuration conventions and local hook-writing functions; they do not establish an automatic npm-triggered mutation.
- Device reporting requires saved credentials and recorded local enforcement state before posting to the configured Intutic API.
- Daemon installation is exposed as an explicit CLI command with required workspace credentials; no automatic package installation trigger was found.
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@1.10.1.
See all versions of @intutic/cli for other recorded verdicts.
- Review the evidence and your use of @intutic/cli@1.10.1 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.