@oked/claude-code@0.6.0
OKed for Claude Code - zero-code human approval for sensitive actions
AI Security Review
scanned 28d ago · by lpm-firewall-aiThe package explicitly configures a Claude Code tool hook when its `init` command is run, which is a warning-level agent capability under the review policy. Its manifest has no automatic npm install hook, and the inspected source does not show a concrete malicious chain.
Decision evidence
public snapshot- The manifest declares only a prepublish hook, so npm installation does not automatically configure Claude Code.
- The CLI resolves project settings to `.claude/settings.json` and writes a command hook into `PreToolUse` when `init` runs.
- The installed hook is `oked-hook`, matched to Bash, Write, Edit, Agent, and MCP tools.
- The `init` command pairs the device with `api.oked.ai` and saves the returned API key to the OKed user config.
- Hook setup is triggered by the explicit `init` command rather than an npm lifecycle hook.
- Pairing uses the package-aligned `api.oked.ai` service; the inspected source did not establish credential forwarding to an unrelated recipient.
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.0.
See all versions of @oked/claude-code for other recorded verdicts.
- Review the evidence and your use of @oked/claude-code@0.6.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.