@oked/claude-code@0.6.5
OKed for Claude Code - zero-code human approval for sensitive actions
AI Security Review
scanned 19d ago · by lpm-firewall-aiThe manifest has no npm install lifecycle hook, and the inspected settings changes are initiated by `oked init`. User-level changes are limited to upgrading an existing OKed hook, so no attack surface was established.
Decision evidence
public snapshot- package.json lists `prepublishOnly` as `npm run build`; no install lifecycle hook is present in its scripts.
- The CLI targets the current project’s `.claude/settings.json`; its hook configuration describes writes and upgrades through `oked init`.
- The CLI adds a hook to project settings when none exists, as part of `init`.
- User-level settings upgrades leave files without an existing `oked-hook` entry unchanged.
- Running `oked init` can update an existing `oked-hook` entry in user-level Claude settings, affecting all projects.
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.5.
See all versions of @oked/claude-code for other recorded verdicts.
- Review the evidence and your use of @oked/claude-code@0.6.5 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.