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

@1time/cli

v0.2.0

Published

Command-line client for end-to-end encrypted one-time secret sharing on 1time.io

Readme

1time CLI

1time is a command-line client for 1time.io, an end-to-end encrypted one-time secret sharing service.

Use it to share passwords, API keys, tokens, private notes, and other sensitive text as self-destructing links from your terminal.

Why Use 1time CLI

  • End-to-end encrypted: the secret is encrypted locally before it is sent to the server.
  • One-time links: once the recipient opens the link, the stored payload is deleted.
  • Simple terminal workflow: pipe a secret in, get a secure link out.
  • Good for developer secrets: API keys, access tokens, SSH snippets, passwords, and incident-response notes.

Quick Start

Install from npm:

npm install -g @1time/cli

Create a one-time link from stdin:

printf 'my-api-key' | 1time send

Read a one-time link:

1time read 'https://1time.io/v/#...'

How It Works

  1. You send a secret from your terminal.
  2. The CLI encrypts it locally using the same protocol as the web app.
  3. The backend stores only ciphertext plus an authentication token.
  4. The recipient opens the one-time link and decrypts the payload with the key material stored in the URL fragment.

The server does not receive the plaintext secret.

Install

From npm:

npm install -g @1time/cli

From this repository:

cd cli
npm install -g .

Requires Node.js 20+.

Commands

1time send

Create an encrypted one-time link.

Input precedence:

  1. piped stdin
  2. 1TIME_SECRET
  3. positional secret argument

Examples:

printf 'postgres://user:pass@host/db' | 1time send
1TIME_SECRET='sk_live_123' 1time send
1time send 'temporary-password-123'

Use a custom host:

printf 'hello' | 1time send --host 1time.io
printf 'hello' | 1time send --host https://1time.io
printf 'hello' | 1time send --host http://127.0.0.1:8080

1time read <link>

Fetch and decrypt a one-time link.

Examples:

1time read 'https://1time.io/v/#...'
1time read --host http://127.0.0.1:8080 'http://127.0.0.1:8080/v/#...'

Command Reference

  • --host <host-or-origin>
  • -h, --help

Host Rules

  • default host is 1time.io
  • bare hosts like 1time.io are normalized to https://1time.io
  • https://... is accepted
  • http://... is rejected except for loopback hosts such as 127.0.0.1

Security Notes

  • Prefer stdin for send.
  • 1time send 'secret' is supported for convenience, but it is insecure because command-line arguments can leak through shell history and process listings.
  • 1time read <link> also places the full secret link in command history and process listings. In this protocol, the URL fragment contains the decryption material.
  • This early version does not yet support passphrases or custom expiry from the CLI.

Current Limitations

  • no passphrase support yet
  • no custom expiry support yet
  • read currently accepts the link as a command argument only

Local Development

Run directly from the repository root:

node cli/index.mjs --help
printf 'hello' | node cli/index.mjs send
node cli/index.mjs read 'https://1time.io/v/#...'

Run tests:

cd cli
npm test

Release

Publish from cli/ so npm uses this README for the package page:

cd cli
npm login
npm pack --dry-run
npm publish --access public

The package syncs the shared protocol before npm test, npm pack, and npm publish, so the published CLI includes the current encryption logic.