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

@napi-rs/keyring

v2.1.2

Published

https://github.com/hwchen/keyring-rs Node.js binding via https://napi.rs

Readme

@napi-rs/keyring

https://github.com/Brooooooklyn/keyring-node/actions Downloads

https://github.com/hwchen/keyring-rs Node.js binding via https://napi.rs

Usage

import { Entry } from '@napi-rs/keyring'

const entry = new Entry('my_service', 'my_name')
entry.setPassword('topS3cr3tP4$$w0rd')
const password = entry.getPassword()
console.log('My password is ', password)
entry.deletePassword()

Linux backend selection

On Linux, Entry and AsyncEntry pick a credential store automatically: the Secret Service (gnome-keyring, KWallet, keepassxc, ...) is tried first, and the binding silently falls back to the kernel keyutils keyring when no Secret Service is available.

You can pin an entry to one specific store by passing the options bag as the last argument (the option is accepted on every platform but only meaningful on Linux):

new Entry('my_service', 'my_name', { linux: { store: 'secret-service' } }) // require Secret Service
new Entry('my_service', 'my_name', { linux: { store: 'keyutils' } }) // require the kernel keyring
Entry.withTarget('target', 'my_service', 'my_name', { linux: { store: 'keyutils' } })

When a store is required, the constructor throws if that store is unavailable — there is no silent fallback. When withTarget is combined with the keyutils store, the target is used as the kernel key description, so distinct targets keep distinct credentials.

Note: the keyutils store keeps credentials in kernel memory: per the linux-keyutils-keyring-store docs, the key management facility "is completely in-memory and will not persist across reboots". Prefer secret-service for credentials that must survive a restart.

Bundled Rust dependencies

The prebuilt .node binaries are built with --locked from the committed Cargo.lock, and with cargo auditable, which embeds the exact list of Rust crates compiled into each binary. Recover it for license compliance or vulnerability scanning with:

cargo install rust-audit-info
rust-audit-info node_modules/@napi-rs/keyring-darwin-arm64/keyring.darwin-arm64.node

# or scan for known vulnerabilities
cargo audit bin node_modules/@napi-rs/keyring-darwin-arm64/keyring.darwin-arm64.node

syft, trivy and grype read the same data.

Each platform package also ships a LICENSE.third-party.md with the license texts of those crates, generated by cargo-about. After changing Cargo.lock, regenerate them with yarn licenses (needs cargo install --locked cargo-about --features cli); CI fails while they are stale.

Note: the Linux binaries statically link libdbus (built from the sources vendored by libdbus-sys), which is licensed under AFL-2.1 OR GPL-2.0-or-later rather than the crate's own MIT OR Apache-2.0. The Linux LICENSE.third-party.md files include its license and copyright notices.