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

@autonoma-ai/envsync

v2.0.1

Published

An NPM package that retrieves secrets from AWS Secrets Manager and writes them to an .env file.

Readme

envsync

envsync is a Node.js package that fetches secrets from AWS Secrets Manager and stores them in an environment file. This helps in keeping secrets secure while ensuring they are available for your application during development. ⚡

✨ Features

  • 🔐 Automatically downloads and updates secrets from AWS Secrets Manager
  • 📄 Stores secrets in an .env file for easy access
  • 🚀 Prevents unnecessary downloads by checking the secret version
  • ⚙️ Configuration stored in package.json
  • 🔑 Uses the default AWS credential chain on the user's system (env vars, ~/.aws/credentials, SSO, IAM roles)
  • 🛠️ Designed for development environments only

📥 Installation

Install envsync as a dev dependency:

npm install @autonoma-ai/envsync --save-dev

⚙️ Configuration

Add the following configuration in your package.json file:

"envsync": {
  "secretName": "your-secret-name",
  "envFile": ".env",
  "region": "us-east-1"
}
  • secretName: The name (or ARN) of the secret in AWS Secrets Manager
  • envFile: The target file where the secret will be stored
  • region (optional): AWS region. If omitted, the SDK uses AWS_REGION / AWS_DEFAULT_REGION or your configured profile's region.

🔐 Credentials

envsync uses the standard AWS SDK credential provider chain, so it picks up whatever your system already has configured. In order, it will look at:

  1. Environment variables (AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN)
  2. Shared credentials file (~/.aws/credentials) — honors AWS_PROFILE
  3. SSO / IAM Identity Center
  4. ECS / EC2 instance metadata

No credential configuration is required from the package itself.

🗂️ Secret format

The secret payload is written to envFile verbatim, so store it in AWS Secrets Manager as the raw contents of a .env file, e.g.:

DATABASE_URL=postgres://...
API_KEY=sk-...

🚀 Usage

You can use envsync programmatically within your Node.js application:

import { saveSecretToEnv } from '@autonoma-ai/envsync';

await saveSecretToEnv();

Alternatively, add a script in package.json to run it easily:

"scripts": {
  "fetch-secret": "node -e \"import('@autonoma-ai/envsync').then(({ saveSecretToEnv }) => saveSecretToEnv())\""
}

Run the script with:

npm run fetch-secret

🔄 How It Works

  1. 📝 envsync reads the configuration from package.json.
  2. 🔑 It fetches the latest version of the secret from AWS Secrets Manager (using AWSCURRENT).
  3. 🛑 If the secret VersionId matches the one tracked in the .env file, it skips the update.
  4. ✅ If the version is different, it updates the .env file with the new secret and records the new VersionId.

⚠️ Important

envsync is designed for development environments only! 🚧 Do not use it in production to prevent security risks.

🔧 Requirements

  • 📌 Node.js 14+
  • ☁️ AWS credentials configured on the system with secretsmanager:GetSecretValue permission for the target secret

📜 License

MIT