@oked/claude-code@0.6.3
OKed for Claude Code - zero-code human approval for sensitive actions
AI Security Review
scanned 28d ago · by lpm-firewall-aiSource inspection shows a user-invoked command that modifies Claude Code project settings and installs a hook matching broad tool actions. This is a warning-level agent capability, with no evidence of unconsented install-time mutation or credential exfiltration.
Decision evidence
public snapshot- The package exposes the `oked` CLI and has no npm install lifecycle hook.
- Running `oked init` adds or updates an OKed command hook in the project’s Claude settings.
- The hook matches Bash, file editing, agent, and MCP tool actions.
- Pairing sends a device-code request to the configured OKed backend and saves the returned key after pairing.
- The settings change is performed by the explicit `init` command, not by an npm install hook.
- Pairing uses the package’s OKed backend and requires the user to complete device approval.
Source & flagged code
6 flaggedA single source file combines environment access, network access, and code or shell execution; review context before blocking.
dist/cli.jsView on unpkg · L4Findings
Affected versions and remediation
This report applies to @oked/claude-code@0.6.3.
See all versions of @oked/claude-code for other recorded verdicts.
- Review the evidence and your use of @oked/claude-code@0.6.3 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.