npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@oked/claude-code

v0.3.6

Published

OKed for Claude Code - zero-code human approval for sensitive actions

Readme

@oked/claude-code

npm version License: MIT

Zero-code integration for Claude Code. Installs a PreToolUse hook that routes sensitive actions (destructive Bash commands, payment MCP tools, etc.) through the OKed backend and waits for a human decision before Claude Code proceeds.

Non-dangerous actions are left to Claude's normal permission flow - OKed only intervenes when it matters.

Install

npm install -g @oked/claude-code
oked init

oked init writes a PreToolUse hook entry into the current project's .claude/settings.json, opens OKed's device-pairing flow in your browser, and stores the paired API key in ~/.oked/config.json. Open a new Claude Code session in that project to activate the hook.

Commands

| Command | What it does | |---|---| | oked init | Install or update the project hook and pair this device. | | oked status | Show install state and ping the backend. | | oked uninstall | Remove the project hook entry (other hooks are preserved). |

What gets intercepted

The hook uses a four-tier classifier. Classification is effect-based: it detects the kind of effect an action has rather than matching specific command names, and defaults to no prompt. Only destructive, irreversible, or outward-facing operations put a human in the loop.

| Tier | Behavior | Examples | |---|---|---| | safe | Auto-allow, no notification | Reads & queries, a DB SELECT, and any command with no detected side effect — ls, grep, jq, node, npx, plain curl GET (the default) | | warning | Terminal log only, no push | A reversible local mutation: file create / cp / mv, a /tmp delete, local git (add/commit), npm install, SQL INSERT/CREATE | | review | Push notification, tap to approve | Sensitive-path writes (~/.ssh, shell rc, system dirs, OKed config), sudo, outward message/email sends, MCP create_* / send_* / update_* | | high_stakes | Push notification with confirmation | Destructive / irreversible / external: rm of non-temp data, DROP TABLE / DELETE FROM, git push / reset --hard / branch -D, mkfs / dd-to-device / shutdown, curl POST/DELETE, ssh/scp, npm publish, kill |

A Bash command that matches none of the prompt-worthy effect categories defaults to safe — running a command is not, by itself, something we interrupt you for. (Unknown non-Bash tools still default to review.)

How it works

  1. Claude Code fires the PreToolUse hook before every tool call.
  2. The hook classifies the action locally (no network call for safe actions).
  3. If it's high-stakes, it sends an approval request to the OKed backend.
  4. You get a notification (Telegram, web push, or dashboard).
  5. Approve or deny - Claude waits for your decision.

Environment

| Var | Required | Description | |---|---|---| | OKED_API_KEY | no, after pairing | Optional override. oked init normally stores the paired key in ~/.oked/config.json. | | OKED_BACKEND_URL | no | Override the hosted backend URL. | | OKED_STRICT_FAIL_CLOSED | no | Set to 1 or true to deny every sensitive action when the backend is unreachable. |

Degraded-mode behavior

Explicit denials and invalid API keys deny the action. If the backend is unreachable, OKed denies high_stakes actions and, by default, allows lower tiers so a temporary outage does not stop every Claude Code workflow. If no API key is configured, the hook returns ask so Claude Code's native permission flow can handle the decision. Set OKED_STRICT_FAIL_CLOSED=1 to deny every sensitive action during backend outages.

License

MIT