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

lianki

v0.1.5

Published

Command-line client for Lianki (FSRS spaced-repetition) — agent-friendly.

Downloads

582

Readme

lianki

Command-line client for Lianki — an FSRS spaced-repetition app. Built for agents and scripts: non-interactive auth, and every data command prints the server's JSON verbatim to stdout.

npx lianki help

Auth

Mint an API token in the Lianki web UI (Settings → API Tokens); it looks like lk_…. Provide it any of these ways (checked in order):

  1. --token lk_… flag (per call)
  2. LIANKI_TOKEN environment variable
  3. saved config: lianki login lk_…~/.config/lianki/config.json
export LIANKI_TOKEN=lk_xxx          # agents: set once in the environment
# or
npx lianki login lk_xxx             # humans: persist to ~/.config/lianki
echo "$TOKEN" | npx lianki login    # or pipe via stdin
npx lianki whoami                   # verify

Commands

| Command | Description | | --- | --- | | add <url> [--title T] | Add a card | | due [--limit N] | List due cards (--exclude-domains a,b) | | next | Next due card's url (--exclude-url U, --exclude-domains a,b) | | get <url> | Fetch one card by url | | review <url> <again\|hard\|good\|easy> | Grade a card | | delete <url> | Delete a card | | move <oldUrl> <newUrl> | Change a card's url | | export [--out FILE] | Export everything as YAML | | import <file.yaml> | Restore from a YAML export | | login / logout / whoami | Manage / verify the saved token |

Ratings accept again hard good easy or 1 2 3 4.

Output contract

  • Success: JSON to stdout, exit 0. (export prints raw YAML.)
  • Failure: {"error":…} (plus status for HTTP errors) to stderr; exit 2 for auth errors (401/403), 1 otherwise.

This makes it safe to pipe into jq/node -pe and to branch on exit code:

url=$(npx lianki next | jq -r .url)
[ "$url" != "null" ] && npx lianki review "$url" good

Targeting a different backend

Point at any Lianki-compatible API (e.g. a preview/staging worker) with --api or $LIANKI_API:

LIANKI_API=https://lianki-cf.snomiao.workers.dev npx lianki due

Defaults to https://www.lianki.com.

Requirements

Node ≥ 18 (uses the built-in global fetch). Only runtime dependency: yargs.