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

@sevenofnine-ai/proton-drive-cli

v0.1.2

Published

End-to-end encrypted CLI for Proton Drive with Git LFS bridge support

Readme

Proton Drive CLI

End-to-end encrypted CLI for Proton Drive with Git LFS bridge support, powered by the official @protontech/drive-sdk.

Documentation npm version Tests

Documentation

📚 Complete Documentation with:

Installation

corepack enable
yarn install
yarn build

For local development, invoke the CLI directly with node dist/index.js.

Credential Providers

Passwords are never accepted via CLI flags or environment variables. This prevents leaks via ps, /proc/pid/environ, and shell history.

Git Credential Manager (recommended)

Uses the system credential helper (macOS Keychain, Windows Credential Manager, Linux Secret Service) via git credential fill.


# Store credentials in the system credential helper

proton-drive-cli credential store -u [email protected]

# Verify credentials are stored

proton-drive-cli credential verify

# Login using stored credentials

proton-drive-cli login --credential-provider git

# Use with any command

proton-drive-cli ls / --credential-provider git

# Remove stored credentials

proton-drive-cli credential remove -u [email protected]

pass-cli (Git LFS integration)

When used through proton-git-lfs, the Go adapter resolves credentials via pass-cli and spawns proton-drive-cli bridge directly, passing credentials over stdin. Do not run proton-drive-cli login manually in this mode.


pass-cli → Go adapter → proton-drive-cli bridge (stdin, memory only)

Piped stdin (scripted usage)

For CI or scripted environments where git-credential is not available:

printf '%s' 'password' | proton-drive-cli login -u [email protected] --password-stdin
printf '%s' 'password' | proton-drive-cli credential store -u [email protected] --password-stdin

Usage

Authentication


# Login with git-credential (recommended)

proton-drive-cli login --credential-provider git

# Login with piped password

printf '%s' 'your-password' | proton-drive-cli login -u [email protected] --password-stdin

# Check authentication status

proton-drive-cli status

# Logout

proton-drive-cli logout

Session tokens (no passwords) are stored in ~/.proton-drive-cli/session.json with 0600 permissions. Tokens are refreshed automatically on HTTP 401 and Proton error code 9101.

CAPTCHA: If CAPTCHA verification is required during login, the CLI guides you through the semi-automated token extraction process.

File Operations


# List files

proton-drive-cli ls /
proton-drive-cli ls /Documents --long

# Upload files

proton-drive-cli upload ./file.pdf /Documents
cat data.json | proton-drive-cli upload - /Documents --name data.json

# Download files

proton-drive-cli download /Documents/file.pdf ./file.pdf

# Create folders

proton-drive-cli mkdir /Documents Projects

# Show file/folder metadata

proton-drive-cli info /Documents/file.pdf

# Stream file contents to stdout

proton-drive-cli cat /Documents/file.txt

# Move or rename files/folders

proton-drive-cli mv /Documents/old-name.pdf /Documents/new-name.pdf

# Remove files/folders

proton-drive-cli rm /Documents/old-file.pdf
proton-drive-cli rm /Documents/old-file.pdf --permanent

Global Options

| Flag | Description | | ----------------------- | ------------------------------------------------- | | -d, --debug | Enable debug output with full stack traces | | --verbose | Show detailed output (spinners, progress, tables) | | -q, --quiet | Suppress all non-error output | | -v, --version | Display version number | | --credential-provider | Credential source: git or default (stdin) |

Developer Documentation

See docs/ for detailed documentation:

When docs disagree, runtime behavior and tests win.

Testing

yarn test                        # Run all tests (fully mocked)
yarn test --no-cache             # Without cache
npx jest src/sdk/                # SDK adapter tests only
npx jest src/cli/e2e.test        # E2E CLI tests

All tests are fully mocked and CI-safe — no Proton credentials required.

License

MIT