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

@lockr-dev/cli

v1.0.1

Published

Command-line interface for Lockr secrets management - securely pull, sync, and inject environment variables

Readme

Lockr CLI

A command-line interface for managing secrets with LockrDev.

Installation

npm install -g @lockr-dev/cli
# or
npx @lockr-dev/cli

Authentication

First, create an API token in the Lockr dashboard:

  1. Go to IntegrationsAPI Tokens (Pull)
  2. Click Create API Token
  3. Copy your token

Then authenticate:

lockr auth login --token YOUR_API_TOKEN
# or set the environment variable
export LOCKR_API_TOKEN=YOUR_API_TOKEN

Commands

Pull Secrets

Pull secrets from Lockr to your local environment:

# Pull all secrets for production
lockr pull --env production

# Pull to a specific file
lockr pull --env production --output .env

# Pull specific keys only
lockr pull --env production --keys API_KEY,DATABASE_URL

# Output as JSON
lockr pull --env production --format json

Run with Secrets

Run a command with secrets injected as environment variables:

# Run your app with production secrets
lockr run --env production -- npm start

# Run with staging secrets
lockr run --env staging -- docker-compose up

List Environments

lockr envs list

Whoami

Check your current authentication:

lockr whoami

Configuration

Create a .lockrrc file in your project root:

{
  "project": "my-project",
  "defaultEnv": "development"
}

CI/CD Usage

GitHub Actions

steps:
  - name: Pull secrets
    run: npx @lockr-dev/cli pull --env production --output .env
    env:
      LOCKR_API_TOKEN: ${{ secrets.LOCKR_API_TOKEN }}

GitLab CI

deploy:
  script:
    - npx @lockr-dev/cli pull --env production --output .env
    - docker build -t myapp .
  variables:
    LOCKR_API_TOKEN: $LOCKR_API_TOKEN

CircleCI

jobs:
  build:
    steps:
      - run:
          name: Pull secrets
          command: npx @lockr-dev/cli pull --env production --output .env

Environment Variables

| Variable | Description | |----------|-------------| | LOCKR_API_TOKEN | Your API token for authentication | | LOCKR_API_URL | Custom API URL (default: production) | | LOCKR_PROJECT | Default project to use |

License

MIT