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

tensile-ci

v0.2.0

Published

Tensile: see what's missing before an agent pull request can merge. Select the tests a change can affect, tell your failures from flaky or broken-main ones, and get merge evidence, from your terminal or agent. GitHub and GitHub Actions.

Readme

tensile-ci

Tensile shows what's missing before an agent pull request can merge, from the CI you already run on GitHub Actions. This is its CLI: selecting the tests a change can affect, sorting failures and merge evidence, for people and coding agents. Every command takes --json.

Needs Node 24 or later. Version 0.2.0.

Quickstart

npm install -g tensile-ci        # or: npx tensile-ci --help

tensile --help
tensile select --json            # which tests your change can affect (runs everything when unsure)
tensile precheck                 # the selected tests plus lint, before you push
tensile why "CI / test" --json   # why a check failed, and what to do next
tensile main --json              # is main green or red, since which commit, what broke it
tensile can-merge 12 --json      # may PR #12 merge now, with every reason and its evidence

For coding agents

skills/tensile-ci/SKILL.md is an agent skill that teaches the CLI. Copy it where your agent loads skills, for example cp -r node_modules/tensile-ci/skills/tensile-ci .claude/skills/ for Claude Code. tensile agents-md prints a shorter AGENTS.md / CLAUDE.md snippet. The --json shapes are in schemas/.

jiffy is installed as an alias of tensile.

Exit codes, every command: 0 ready, 1 action needed, 2 waiting (don't change code), 3 needs a human, 4 inconclusive, 5 tool or usage error (no answer).

Without a coverage map, select runs everything when unsure: it never guesses.