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

@borrowbrain/vck

v1.8.0

Published

VCK command-line wrapper.

Vulnerabilities

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

Links

Maintainers

borrowbrain.ioborrowbrain.io

Keywords

Readme

@borrowbrain/vck

VCK command-line wrapper.

Publication requires release readiness approval.

Commands

npx @borrowbrain/vck@latest help
npx @borrowbrain/vck@latest new my-app
npx @borrowbrain/vck@latest connect ../existing-app --repo-url [email protected]:team/app.git --default-branch main
npx @borrowbrain/vck@latest doctor
npx @borrowbrain/vck@latest status
npx @borrowbrain/vck@latest status --json
npx @borrowbrain/vck@latest init
npx @borrowbrain/vck@latest init --help
npx @borrowbrain/vck@latest init --vision-file ./product-vision.md --user "Owner" --profile blank-starter --dry-run
npx @borrowbrain/vck@latest init --development-process tdd --user "Owner" --product-name "Demo App" --dry-run
npx @borrowbrain/vck@latest update
npx @borrowbrain/vck@latest update --confirm
npx @borrowbrain/vck@latest mcp

The commands delegate to existing VCK runtime tools in the repository.

vck status is read-only. Use it before starting or resuming work to see current operator posture and the next legal action.

vck new and vck connect are review-first by default. Use --yes only after reviewing the printed target and bundled clean starter.

vck update runs dry-run review first. Use --confirm only after reviewing the update report.

vck init --development-process <id> selects one primary development process profile for the project. Supported ids are default-governed, tdd, bdd-atdd, ddd, ux-first, api-first, and data-first. VCK blocks conflicted combinations before writing project truth.

If the package is installed globally, the shorter vck doctor form may work. For package testing, prefer the npx @borrowbrain/vck@latest ... form so the tested package version is explicit.

Prompts such as SYS: health check are AI-surface prompts, not terminal commands.