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

@oc-forge/secret

v0.2.0

Published

Infisical secret manager CLI with local caching

Readme

@oc-forge/secret

🔐 Infisical secret manager CLI with local caching.

Manage secrets from Infisical with a simple CLI. Caches secrets locally (24h TTL) to minimize API calls.

Install

# Requires Bun runtime
npm install -g @oc-forge/secret

Setup

Create a config file at ~/.config/oc-secret/config.json:

{
  "clientId": "<your-infisical-client-id>",
  "clientSecret": "<your-infisical-client-secret>",
  "projectId": "<your-infisical-project-id>",
  "env": "dev"
}

Or use environment variables:

export INFISICAL_CLIENT_ID=xxx
export INFISICAL_CLIENT_SECRET=xxx
export INFISICAL_PROJECT_ID=xxx
export INFISICAL_ENV=dev  # optional, defaults to "dev"

Usage

# Get a secret (cache-first)
secret get MY_API_KEY

# Get a secret (skip cache)
secret get MY_API_KEY --fresh

# Set/update a secret
secret set MY_API_KEY "new-value"

# List all secret keys
secret list

# List with values
secret list --show

# Sync all secrets to local cache
secret sync

# Run a command with all secrets as env vars
secret exec -- node server.js

How it works

  1. Cache-first: secret get checks local cache (~/.config/oc-secret/cache.json) before hitting the API
  2. 24h TTL: Cache entries expire after 24 hours (configurable via ttlMs in config)
  3. Upsert: secret set creates or updates the secret on Infisical and updates local cache
  4. Exec: secret exec injects all secrets as environment variables into a child process

Output

  • Secret values go to stdout (clean, no decoration)
  • Status messages go to stderr (won't pollute $(secret get KEY))
# Safe to use in shell substitution
TOKEN=$(secret get MY_TOKEN)

Security

  • Cache file is chmod 600 (owner-only read/write)
  • Credentials never leave your machine
  • Universal Auth (machine identity) — no user login required

License

MIT — 小橘爪作 🐾