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

@syncrona/credential-store

v0.9.0

Published

Shared encrypted credential store for SyncroNow AI (core CLI and MCP server).

Readme

@syncrona/credential-store

| npm: not yet published | node | license | CI | TypeScript | |:--:|:--:|:--:|:--:|:--:|

Shared encrypted credential store for SyncroNow AI. It is the single source of truth for at-rest credential storage used by both the syncrona CLI and the @syncrona/mcp-server, so the encryption format, key derivation, file naming, and on-disk layout never diverge between processes.

Layout

~/.syncrona/
  config.json                 # { "activeInstance": "<instance>" }
  credentials/<instance>.enc  # AES-256-GCM "iv:authTag:ciphertext" (hex)

API

Async (used by the core CLI, read + write):

  • saveCredentials(instance, user, password)
  • loadCredentials(instance) — throws if missing
  • listInstances()
  • removeCredentials(instance) / removeAllCredentials()
  • setActiveInstance(instance) / getActiveInstance()
  • resolveCredentialsFromStore(instance?)
  • getSyncronaDir()

Sync (used by the MCP server during secrets resolution; never throw, return null on any failure):

  • getActiveInstanceSync()
  • loadCredentialsSync(instance)

Low-level primitives are also exported: getStoreKey, getStoreKeySource, getMachineKey, encrypt, decrypt, instanceToFilename, filenameToInstance.

Security

The encryption key is resolved by getStoreKey() with the precedence:

  1. SYNCRONA_STORE_KEY — an explicit 32-byte key (64 hex chars or base64), for CI / secrets managers. Strongest option.
  2. OS keychain (default) — used automatically when the optional @napi-rs/keyring dependency is installed; opt out with SYNCRONA_USE_KEYCHAIN=0 (e.g. a headless CI box with no keychain). A random 256-bit master key is kept in the OS keychain (macOS Keychain / Windows Credential Manager / libsecret).
  3. Machine-derived key (fallback) — obfuscation-grade; derived from the machine hostname and OS username, so anyone able to run as the same user on the same host can decrypt files written with it. Used only when the keychain / @napi-rs/keyring is unavailable (or explicitly disabled).

Reads fall back to the machine-derived key so pre-existing files keep decrypting. getStoreKeySource() reports which path won ("env" / "keychain" / "machine"). See the core README "Credential storage security" section for hardening recommendations.