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

@lastingnote/cli

v1.1.0

Published

CLI for LastingNote dead man's switch check-ins

Downloads

23

Readme

@lastingnote/cli

CLI for LastingNote dead man's switch check-ins. Designed for AI assistants (Claude Code, etc.) and automation scripts.

Installation

npm install -g @lastingnote/cli

Setup

  1. Create an API key in the LastingNote web app (Settings > API Keys)
  2. Configure the CLI with one of:
# Option A: Environment variable (recommended)
export LASTINGNOTE_API_KEY=lnk_your_key_here

# Option B: Config file
echo "api_key=lnk_your_key_here" > ~/.lastingnote

Usage

Check status

lastingnote status
# Last check-in: 3 days ago. Next due in 27 days. Status: OK

Perform a check-in

lastingnote checkin
# Checked in successfully.

View history

lastingnote history
# Date                        Type
# --------------------------------------------------
# 2026-03-13 10:00:00          API Key - Claude
# 2026-03-10 10:00:00          Mobile

JSON output

All commands support --json for machine-readable output:

lastingnote status --json
{
  "status": "ok",
  "lastCheckIn": "2026-03-13T10:00:00Z",
  "nextDue": "2026-04-12T10:00:00Z",
  "deadline": "2026-04-19T10:00:00Z",
  "daysUntilDue": 27,
  "daysUntilDeadline": 34
}

Exit Codes

| Code | Meaning | |------|---------| | 0 | Success / status OK | | 1 | Error (network, auth, invalid config) | | 2 | Action needed (overdue, grace period, frozen) |

Exit codes enable scripting:

# Exit code 2 = action needed; exit code 1 = error (don't retry blindly)
lastingnote status; [ $? -eq 2 ] && lastingnote checkin

AI Assistant Integration

Claude Code

Add to your project's CLAUDE.md:

After completing work, run `lastingnote status` and check me in if needed.

Or use it directly:

> run `lastingnote status` and check me in if needed

MCP / Tool Use

Use --json for structured output:

lastingnote status --json
lastingnote checkin --json

Configuration

Precedence (highest to lowest):

  1. --api-key <key> flag
  2. LASTINGNOTE_API_KEY environment variable
  3. ~/.lastingnote config file (api_key=lnk_...)

Environment Variables

| Variable | Description | |----------|-------------| | LASTINGNOTE_API_KEY | API key (lnk_...) | | LASTINGNOTE_URL | Override API base URL (for development) |

Development

cd tools/lastingnote-cli
npm install
npm run build
npm test