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

@jami-studio/harness-cli

v0.1.1

Published

Agent-first CLI foundation for local Jami Harness runs and evidence inspection.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

jamienavinjamienavinjamesnavinhilljamesnavinhill

Keywords

Readme

Jami Harness CLI Foundation

Status: local foundation

@jami-studio/harness-cli provides the first agent-facing local command surface for the existing harness packages.

Current commands:

  • jami init --json creates .jami-harness/harness.json idempotently.
  • jami run --json executes the local deterministic provider workflow through the SDK, policy-gated local tool gateway, evidence packet export, and checkpoint store. It writes run evidence under .jami-harness/runs/<runId>/ plus a redacted checkpoint under .jami-harness/checkpoints/.
  • jami run --json --provider-id provider_openai fails closed as an unsupported external provider route with a nonzero exit code; no hosted provider API is called.
  • jami run --json --provider-failure-mode fail_once records recoverable provider failure evidence before deterministic retry.
  • jami resume --json --run-id <runId> reports checkpoint replay status and replay hash.
  • jami approve --json --run-id <runId> --action-id <actionId> records a local approval decision through the checkpoint store.
  • jami deny --json --run-id <runId> --action-id <actionId> records a local denial decision through the same approval evidence contract.
  • jami cancel --json --run-id <runId>, jami retry --json --run-id <runId>, and jami migration --json are explicit fail-closed JSON surfaces until runtime cancellation, manual retry orchestration, and checkpoint/store migration runners exist.
  • jami inspect --json reports latest run evidence, checkpoint state, approvals, and active module capabilities.
  • jami doctor --json reports module, checkpoint, resume, and missing optional capability diagnostics.
  • jami tools --json reports tool adapter manifests, source-lock states, supported function/trusted MCP fixture paths, and fail-closed unavailable adapters.
  • jami memory --json, jami context --json, jami docs --json, and jami map --json report current capability availability plus the full local source-checkout install path and modular BYO replacement paths; jami map --json also includes tool adapter inspection.
  • jami workbench --json reports local static workbench generation/check commands and keeps hosted workbench/control, hosted stores, and Studio UI package integration explicitly unavailable or unclaimed.
  • jami release --json reports the non-publishing release audit surface and unavailable public publishing/provenance/attestation routes without publishing, tagging, deploying, or calling external account APIs.
  • jami verify --json checks local CLI state and core module availability with clean exit codes, including the generated full-local and modular replacement path manifest.

Malformed run and action identifiers are rejected with structured JSON errors before the CLI reads or writes run state.

The CLI reports the local deterministic provider and tool gateway foundations as available for provider replacement-port inspection, policy-gated function execution, trusted MCP fixture execution, and unsupported adapter/provider manifests with source-lock evidence. Local filesystem checkpoint/resume and approval evidence are available through @jami-studio/harness-store-local. Repo-level docs generation exists through pnpm docs:generate and is recorded in docs/generated/install-readiness-manifest.json; the CLI docs capability still reports SDK docs-output injection as not wired. A dependency-free local static workbench is generated through pnpm workbench:generate from current SDK/CLI/runtime evidence and generated docs manifests. Public package installation, hosted workbench, hosted stores, hosted provider runtime, Mintlify build/publish, and full MCP/OpenAPI/ shell/browser/code/provider-as-tool/A2A execution remain unavailable until those surfaces exist with current source-lock evidence.