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

@parsemend/cli

v0.1.3

Published

Parsemend CLI runner — pull a fix context bundle and run the fix pipeline locally with your own model keys.

Readme

@parsemend/cli

The Parsemend CLI runner (§4.8 of the platform design spec): pulls a fix context bundle for an issue from your Parsemend instance and runs the same root-cause → solution → coding pipeline locally, against your own working copy, using your own model keys (or a local claude CLI handoff). Source code is never uploaded to Parsemend's servers — only the opt-in post-back sends root-cause/diff data back, never files.

Install

npm install -g @parsemend/cli
# or, from this repo:
npm install && npm run build && npm link

Requires Node 20+.

Usage

parsemend login                # store your personal API token
parsemend fix <issue-url|id>   # run the pipeline
parsemend post-back <issue-id> # publish a prior local run's results
parsemend logout
parsemend upgrade              # update to the latest published version
parsemend --version

qa commands (CI-facing)

parsemend qa run and parsemend qa export are the qa-C CI/PR-gating surface: they authenticate with a durable org token (PARSEMEND_ORG_TOKEN env var, checked first, else --token) rather than the personal login token, since CI doesn't run an interactive login.

parsemend qa run --suite <name> --org <slug> --project <slug> [--base-url <url>] [--environment <name>] [--wait] [--json]
parsemend qa export --org <slug> --project <slug> [--out <file>]

qa run triggers a suite run; with --wait it polls until the run reaches a terminal status (passed/failed/errored) and exits 0 iff passed — raw pass/fail only, never gated by per-flow triage verdicts. --sha, --branch, --pr-number, and --repository pass GitHub context through for the server's check-run/Issue-link reporting. qa export lists a project's flow definitions as YAML.

See docs/ci-example.md for a full GitHub Actions example that blocks a job on qa run --wait's exit code.

Security note

parsemend login writes ~/.parsemend/config.json, containing your personal API token in plaintext and, if you configure them, your own provider API keys. The file is written 0600 (and its directory 0700), which restricts it on POSIX systems (macOS/Linux). This offers no protection on Windows — that platform is out of scope for this version.

Configuration

The CLI talks to https://api.parsemend.com by default, so login only really needs your token — press enter at the base-URL prompt. Set PARSEMEND_API_URL (or answer that prompt) to point at a self-hosted or staging deployment; the environment variable wins over the saved config.

Model roles (explore/conclude/format/code) resolve from, in order: a CLI flag, a PARSEMEND_MODEL_<ROLE> environment variable (e.g. PARSEMEND_MODEL_EXPLORE=anthropic:claude-haiku-4-5), or a built-in default. Supported providers: anthropic, openai, google, ollama (served via an OpenAI-compatible local endpoint).

Tests

npm test

License

MIT — see LICENSE.