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

@lockzero/render-lockzero

v1.0.0

Published

Sync LockZero secrets to Render.com environment variables via the Render API v1

Downloads

137

Readme

@lockzero/render-lockzero

Sync secrets from your LockZero vault into Render.com environment variables via the Render API v1.

Installation

npm install -g @lockzero/render-lockzero

Or use npx:

npx @lockzero/render-lockzero sync --help

CLI Usage

lockzero-render sync \
  --lz-key    lz_live_... \
  --render-key rnd_... \
  --service   srv_... \
  --namespaces openai,stripe \
  --prefix     ""

Options

| Flag | Required | Default | Description | |-----------------|----------|---------------------|----------------------------------------------------| | --lz-key | Yes* | LOCKZERO_API_KEY env | LockZero API key | | --render-key | Yes* | RENDER_API_KEY env | Render API key from render.com/u/settings | | --service | Yes | — | Render service ID (e.g. srv_abc123) | | --namespaces | Yes | — | Comma-separated LockZero namespaces | | --prefix | No | "" | Prefix for injected variable names |

*Can also be set via environment variable.

How it works

  1. Fetches existing Render env vars for the service (to preserve non-LockZero variables).
  2. For each namespace, fetches all fields from LockZero via GET /api/credentials/:namespace.
  3. Merges the new values into the existing set (LockZero values take precedence for matching keys).
  4. Writes the merged set back via PUT /services/:id/env-vars.

Render's PUT /env-vars is a full-replace operation, so the merge step ensures you don't accidentally delete manually-set variables.

Programmatic API

import { syncToRender } from "@lockzero/render-lockzero";

const result = await syncToRender({
  lzApiKey:    "lz_live_...",
  renderApiKey: "rnd_...",
  serviceId:   "srv_...",
  namespaces:  ["openai", "stripe"],
  prefix:      "",
});

console.log(`Synced ${result.synced} variables`);
if (result.errors.length) {
  console.error("Errors:", result.errors);
}

Getting a Render API Key

  1. Go to https://render.com/u/settings
  2. Scroll to API KeysCreate API Key.
  3. Use it as --render-key or RENDER_API_KEY.

Finding your Service ID

In the Render dashboard, open your service. The ID is in the URL: https://dashboard.render.com/web/srv-XXXXX → service ID is srv-XXXXX.