---
title: "@napi-rs/keyring 2.1.2: release notes, upgrades and advisories"
description: "@napi-rs/keyring 2.1.2: release notes, breaking changes by major version and no known security advisory."
url: https://inlinr.com/packages/@napi-rs/keyring
lang: en
---

[Packages](https://inlinr.com/packages)

# @napi-rs/keyring

2.1.2 · 19 Oct 2026 MIT 8.9M / week [Repository](https://github.com/Brooooooklyn/keyring-node) [Homepage](https://github.com/Brooooooklyn/keyring-node#readme) [npm](https://www.npmjs.com/package/@napi-rs/keyring) [Atom feed](https://inlinr.com/packages/feed/@napi-rs/keyring)

Your version 

## Where each line stands

[Plan an upgrade](https://inlinr.com/packages/@napi-rs/keyring/upgrade)

LineNewestSecurity

- 2.x 2.1.2 No known advisory Latest line
- 1.x 1.3.0 No known advisory [To 2.1.2](https://inlinr.com/packages/@napi-rs/keyring/upgrade/1.3.0-2.1.2)
- 0.x 0.0.1 No known advisory [To 2.1.2](https://inlinr.com/packages/@napi-rs/keyring/upgrade/0.0.1-2.1.2)

## Latest releases

1. 2.x · latest line
2. ### [2.1.2](https://inlinr.com/packages/@napi-rs/keyring/releases/2.1.2 "Open this release") [](https://github.com/Brooooooklyn/keyring-node/releases/tag/v2.1.2 "Read this release where it was published")  
19 Oct 2026  
Only updates dependencies, nothing else changes.
3. ### [2.1.1](https://inlinr.com/packages/@napi-rs/keyring/releases/2.1.1 "Open this release") [](https://github.com/Brooooooklyn/keyring-node/releases/tag/v2.1.1 "Read this release where it was published")  
10 Oct 2026

  - Type async getPassword/getSecret as null for missing entries
4. ### [2.1.0](https://inlinr.com/packages/@napi-rs/keyring/releases/2.1.0 "Open this release") [](https://github.com/Brooooooklyn/keyring-node/releases/tag/v2.1.0 "Read this release where it was published")  
13 Sep 2026

  - Allow selecting the Linux credential store explicitly

Dependency tracking

## Know when your own dependencies move

@napi-rs/keyring shipped a new major in the last 12 months, among 5 releases. inlinr shows which of your projects are behind, and what the upgrade breaks.

- Advisories reach you  
An email when a critical or high advisory affects a project, before the next install.
- Upgrades checked first  
Peer ranges, Node, ESM-only and types changes read before you bump.
- Only what matters  
Majors and breaking notes stay; patches and sibling bumps fold into one line.

[How dependency tracking works](https://inlinr.com/dependencies)

## Security

No known security advisory.

## Health of 2.1.2

[Details](https://inlinr.com/packages/@napi-rs/keyring/security#signals)

- **Provenance**: Present
- **Publisher**: GitHub Actions
- **Maintainers**: 2
- **Scorecard**: None
- **Size**: 49 kB

## Weekly downloads

## Same family

- [@napi-rs/wasm-runtime 90.4M/wk](https://inlinr.com/packages/@napi-rs/wasm-runtime)
- [@napi-rs/canvas 56.8M/wk](https://inlinr.com/packages/@napi-rs/canvas)

Reading releases, release notes and advisories…

Registry facts last checked 19 Nov 2026\. Releases and advisories last read 19 Nov 2026.

A whole project to check? Paste its package.json in the [dependency check](https://inlinr.com/tools/dependency-check): every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.
