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

@intutic/clawde

v3.2.3

Published

TypeScript SDK for governing Claude and other agents: the gate client, rule records and refusal types

Readme

@intutic/clawde

Programmatic client SDK for intercepting, wrapping, and enforcing policies on AI coding agent scripts.

Installation

npm install @intutic/clawde

Features

  • Governed chat: chat() sends a request through the proxy and resolves with verdict: 'allow'. A governance refusal (policy block, reask, loop run held for review, spend cap, DLP block) throws ClawdeBlockedError with the proxy's verdict, code, ruleId (when the proxy names the rule) and reason, and is never retried; transport failures and 5xx answers are retried, except a 5xx the proxy already retried upstream.
  • Withheld tool calls: when the proxy withholds a tool call from the model's answer (a tool an SOP denies, the SSO group policy, destructive SQL, sensitive output), the answer arrives as a 200 that names the refusal in the x-intutic-refusal and x-intutic-refusal-rule headers. chat() reads them and throws ClawdeBlockedError too. For a stream you read yourself, pass each line to streamRefusal(), which finds the : intutic-refusal marker the proxy writes before the refusal text. See Verdicts and Errors for every refusal code.
  • Verdict Events: client.on('kill' | 'reask' | 'hold', ...) fires on a refusal, before chat() throws.
  • Anthropic requests: provider: 'anthropic' translates OpenAI-style parameters to an Anthropic Messages body, sends it to the proxy's /v1/messages route, and translates the reply back.
  • Budget Check: checkBudget() reports whether the workspace has budget left, from the control plane's GET /api/v1/budget. It needs a control plane address (controlPlaneUrl or INTUTIC_CONTROL_PLANE_URL); without one it throws ClawdeConnectionError, and no session is registered.
  • Circuit Breaker: client.circuitBreaker(toolName, options)(fn) runs fn, after a workspace budget check when requireBudget is set, failing closed unless failOpen is set.
  • Context Resolution: resolveContext() takes each field (git branch, Jira ticket, PagerDuty incident, CI pipeline, workspace, session) from ~/.intutic/config.json when the file carries it, and from environment variables otherwise (GIT_BRANCH, PD_INCIDENT_ID, the CI run id, INTUTIC_WORKSPACE_ID, INTUTIC_SESSION_ID); the Jira ticket comes from the file only.
  • Git context (autoContext, on by default): with an Intutic virtual key, in a git repository, the first chat() registers a session with the control plane carrying the repository (the origin remote as host/path, credentials removed), the branch and the HEAD commit, so the calls count in cost per branch, commit and pull request. Pass autoContext: false to send none of it. See Git context and cost attribution.
  • Control-Plane Management (ControlPlaneClient): The operator APIs the CLI exposes, callable programmatically against the control plane you name (baseUrl or INTUTIC_CONTROL_PLANE_URL; the constructor throws without one): org and workspace setup, gateways, settings and provider credentials, the MCP registry, notification rules, SIEM destinations, usage, the AI inventory, compliance evidence (with verifyEvidenceArchive() to check an archive offline), policy guardrails, held decisions and loop runs, incidents, findings, traces, trace integrity (with verifyIntegrityRoot() to check a sealed root's signature offline), WASM rules, SOPs, API keys (listApiKeys and the rest), the SOP Optimizer's settings (getOptimizerSettings, updateOptimizerSettings) and task-management connections (listTaskConnections). The Python SDK has the same methods in snake_case. See the SDK reference.
  • Decide questions: decide(state, questions, opts) asks a self-hosted model a few narrow yes/no or pick-one questions about a piece of text, written as a decide rule's questions, and returns each answer's probability and reading (with opts.when, the outcome the rule would reach). The engine comes from ~/.intutic/decide/engine.json and the INTUTIC_DECIDE_* variables; a hosted decision API is refused before anything is sent. An engine that is not configured, refused or cannot answer in time throws DecideEngineError. See Decide rules.

Every export, with its signature and defaults: API reference.

License

MIT