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

@lifelinejs/lifeline

v0.1.0

Published

Command-line tool to manage Lifeline branches.

Readme

📦 Lifeline

Command-line tool to manage Lifeline branches.

🌟 Highlights

  • One file describes every line: A single SUPPORT.yaml lists your release lines (3.x, 2.x, …) and their stage, so the lifecycle lives in version control next to the code it describes.
  • Lifecycles are enforced: Lines only travel indev -> as -> ls -> el, and lifeline check shows each branch and its lifecycle.
  • A status table you can read at a glance: lifeline status prints version, stage, branch, whether that branch really exists, the EOL date and the days remaining, or --json for anything scripted.
  • Backports in one command: lifeline backport <sha> --to v1.x cherry-picks a commit from devel onto a support branch and opens the pull request, with a [v1.x]-prefixed title and a body recording where the fix came from. Refuses lines in development or End of Life, and asks for --label security or --label critical before it touches Life Support.

ℹ️ Overview

Lifeline is a CLI to automate your git support branches. Instead of manually backporting or creating LTS branches, you can use Lifeline to do it in less than a second.

✍️ Authors

AI Disclosure: AI was used in the development of Lifeline.

🚀 Usage

Quickly set up Lifeline for your repository:

lifeline init

And then verify it works:

lifeline status

⬇️ Installation

Prerequisites: At least Node.js v22 (Download), and the gh CLI installed (Download).


Find bugs, or want to report a feature? Open an issue, and we'll get to fixing/adding it! If you'd rather implement them yourself, you can also open a pull request. People like you make small OSS projects like these thrive!