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

@jsonl-tools/cli

v0.2.0

Published

Push JSONL files into your jsonl-tools account from a server box — encrypted client-side, readable in the web app.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

virevire

Keywords

jsonlclizero-knowledgeencryptionclaude-codeshare

Readme

@jsonl-tools/cli

Push a JSONL file from a server box into your jsonl-tools account — encrypted on the box before it leaves — and read it later in the web app or pull it back as plaintext. Built for machines with no browser: CI jobs, cron tasks, production hosts, and agents.

bunx @jsonl-tools/cli upload run.jsonl
# → 8f3k…Q2   (the upload's id; it now appears in your My History)

The file is encrypted client-side under a key the server never sees, stored as ciphertext, and decryptable only by you. Same zero-knowledge guarantee as the web share flow, from the command line.

Install

No install needed — run on demand:

bunx @jsonl-tools/cli <command>     # Bun
npx  @jsonl-tools/cli <command>     # Node ≥18

Quick start

  1. Mint a token in the web app: sign in, unlock your account, open the CLI tab, label the box, Create token, and copy the one-time credential.
  2. Seat it on the box:
    bunx @jsonl-tools/cli login        # paste the credential (stdin)
  3. Use it:
    bunx @jsonl-tools/cli upload session.jsonl --title "nightly run"
bunx @jsonl-tools/cli list
bunx @jsonl-tools/cli download --out ./pulled
bunx @jsonl-tools/cli view 8f3k…Q2     # prints an openable web link
bunx @jsonl-tools/cli delete 8f3k…Q2

Configuration

Credential resolution is flag > env > stored file:

  • --token <credential>
  • JSONL_TOOLS_TOKEN
  • the 0600 file written by login (~/.config/jsonl-tools/credentials)

Other flags: --base-url <url> (default https://jsonl-tools.dev), --allow-insecure (permit non-HTTPS, local dev only), --timeout <seconds>, --out <dir> (download), --title <text> (upload).

The base URL must be HTTPS — the credential carries a decryption key, so a cleartext endpoint would leak it.

Security

  • Zero-knowledge. Files are encrypted before any network call; the server stores ciphertext it can't read. download/view decrypt locally.
  • The credential carries a decryption key. Treat it like a password; prefer the 0600 file over --token/env on shared hosts (those leak into ps, shell history, and CI logs).
  • Revoke = stop the box. Revoking a token stops future uploads/reads from that box; it does not un-decrypt data already pushed or pulled.

Full docs: CLI guide · HTTP API · Security model

License

MIT