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

@plenary/cli

v0.5.1

Published

Plenary command-line client: metadata sync, content automation, and a raw API escape hatch.

Readme

@plenary/cli

The plenary command: a client for the Plenary API from a shell, a script, or CI. Sync model and form YAML with an instance, manage entries and media, and call any endpoint.

npm install --save-dev @plenary/cli
npx plenary init                     # writes plenary.json (no secrets)
export PLENARY_API_KEY=pln_prv_…
npx plenary status
plenary metadata pull                # instance → models/ and forms/
plenary metadata diff                # what push would change
plenary metadata push                # apply (never deletes)

plenary entries list post --where status=published --limit 20
plenary entries create post --data '{"title":"Hello"}' --slug hello --publish
plenary entries export post > posts.ndjson

plenary media upload hero.jpg
plenary forms entries export contact > contact.ndjson
plenary api GET models

plenary login                        # a user session, for admin work
plenary api-keys create --name Deploy --grant content:models:update
plenary roles list

Configuration comes from flags, PLENARY_* variables, a .env, then plenary.json. The credential is an API key (content work, CI) or a stored user session from plenary login (admin work); a key wins for content commands when both exist. --json on any command prints the API's JSON; exit 1 is an API error, 2 a usage error.

Full reference: docs/CLI.md in the Plenary repository.