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

@orvain/cli

v0.1.3

Published

Orvain command line: sign in with a licence key and add components to your project

Vulnerabilities

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

Links

Git

Maintainers

oussema.designoussema.design

Keywords

orvainclidesign-systemcomponentsreactvue

Readme

@orvain/cli

The orvain command: sign in with a licence key and copy Orvain components (source, styles and what they depend on) into your React or Vue project. The CLI holds no component source; it fetches it from the Orvain API (https://mcp.orvain.dev, or ORVAIN_API_URL).

orvain add accordion              # free components need no key
orvain login ORVAIN-XXXXX-XXXXX-XXXXX-XXXXX
orvain add flat-button --install  # paid components need a key; --install runs your package manager
orvain list
orvain update
orvain logout                     # frees this computer on your licence

| Command | What it does | |---|---| | login <key> | Checks the key, activates this computer, saves credentials, prints your plan and "computers used x of y". | | logout | Frees this computer on your licence and deletes the saved credentials. | | init | Creates orvain.json (framework, dir, components). Detects React or Vue from package.json; pass --framework react\|vue when it can't. add runs it on first use. | | add <name...> | Names are kebab-case (flat-button). Blocks match by their last segment (progress-bar); if that is ambiguous the choices are listed. Existing files are skipped unless --overwrite. Prints the npm packages to install; --install runs pnpm, yarn, bun or npm (by lockfile). | | list | All components, free ones and installed ones marked. | | update [name...] | Re-fetches installed components. Files you edited are left alone unless --overwrite. |

Exit codes: 0 ok, 1 something to fix on your side (the message says what), 2 network or server problem.

Credentials are stored in ~/.config/orvain/auth.json ($XDG_CONFIG_HOME/orvain/auth.json, or %APPDATA%\orvain\auth.json on Windows) with mode 0600: your key and a random id for this computer. orvain.json also keeps a hash of every file written, which is how update tells your edits from upstream changes.

Tests

pnpm --filter @orvain/cli test runs the unit tests and an end-to-end run against the API in-process with a mocked Keygen. pnpm --filter @orvain/cli test:smoke additionally adds flat-button accordion from the real registry build to fresh React and Vue projects and type-checks them with tsc and vue-tsc; it installs packages from npm, so it is skipped by default.