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

@dharma-ai-labs/agent-fabric

v0.2.31

Published

Local-first CLI for connecting coding agents to Dharma evaluation, orchestration, and signed Skill delivery

Downloads

7,064

Readme

@dharma-ai-labs/agent-fabric

The public dharma CLI connects approved local coding-agent workspaces to the Dharma Agent Fabric control plane. It enrolls an outbound-only signed device, discovers provider capabilities, keeps full trajectories in an encrypted local vault, syncs policy-qualified evidence, executes bounded signed tasks, and installs signed Skill releases with receipts and rollback ancestry.

Start

Requires Node.js 22.20 or later.

npm install --global @dharma-ai-labs/agent-fabric
dharma login \
  --portal-url https://www.dharma-ai.io \
  --organization-id <organization-id>
dharma repositories discover --root "$HOME/work"
dharma repositories connect \
  --repo "$PWD" \
  --provider codex \
  --provider claude \
  --provider hermes \
  --organization-id <organization-id> \
  --policy-revision <dashboard-policy-revision>
dharma repositories status --repo "$PWD" --json

Repeat --provider to attach only the local runtimes that should serve the selected repository agent. Omitting it preserves compatibility by attaching every installed supported provider.

One selected source repository becomes one logical organization agent and one permanent branch in the organization's private Dharma control repository. Connecting that repository from another machine or provider adds an endpoint to the same agent. The CLI derives repository identity from a credential-free normalized Git remote. Repositories without a remote require an explicit stable --repository-key; absolute paths are never identity.

Current provider adapters are Codex, Claude Code, Agy, and Hermes Agent. Run dharma providers list because evidence, task, continuation, Skill installation, activation, and usage capabilities are reported independently.

Agy 1.1.15 Skill activation uses only its supported plugin and sandboxed print interfaces. During onboarding, Dharma adds the narrow read-only command(git status) preflight to Agy's permission allowlist. It never uses --dangerously-skip-permissions. A signed remediation Skill contains a content-bound activation token; Agy must return that token with a fresh nonce before the device signs an active installation receipt. A mismatch restores the previous bundle before the receipt is posted.

Signed workspace registration returns the organization-admin-approved evidence policy from Dharma HQ. The CLI applies that server revision to .dharma/approved-policy.json automatically. Without an active content grant, the policy remains local_analysis; with a current bounded grant, it switches to customer_authorized_content with the server-issued receipt and upload limits. A local flag or hand-edited receipt cannot grant content disclosure. The running relay refreshes this policy from signed workspace registration every minute, so an admin grant or withdrawal does not require a manual sync command.

Local metadata analysis is operational triage, not semantic Cognitive Integrity evaluation. Nuanced scoring and remediation require approved, redacted evidence; missing evidence must produce insufficient_evidence.

After a candidate pull request exists, an organization admin first authorizes the candidate on one exact local endpoint. This is an evaluation-only canary, not release approval:

dharma remediations act \
  --organization-id <organization-id> \
  --target-id <repository-remediation-target-id> \
  --action stage_evaluation \
  --json-body '{"endpointId":"<local-endpoint-id>"}' \
  --confirm

Run dharma skills sync with the returned evaluation authorization ID, then collect 20 later non-source trajectories on that endpoint. The held-out gate rejects trajectories that do not carry the installed candidate bundle ID:

dharma skills sync \
  --workspace-id <workspace-id> \
  --provider <codex|claude|agy|hermes> \
  --policy .dharma/approved-policy.json \
  --approval-id <evaluation-authorization-id>

dharma remediations act \
  --organization-id <organization-id> \
  --target-id <repository-remediation-target-id> \
  --action run_backtest \
  --body-file held-out-trajectories.json \
  --confirm

held-out-trajectories.json contains a trajectoryIds array with 20 to 100 UUIDs for that repository agent. HQ rejects source, older, cross-agent, deleted, or unavailable evidence.

Licensed under MIT. Do not report security vulnerabilities in a public issue; use the private security-reporting channel in the GitHub repository.