Library / SDK
oblador/react-native-keychain avatar
oblador/react-native-keychain

react-native-keychain's README is four install steps and a link, and its four entry points split the build

:key: Keychain Access for React Native

3,489 stars542 forksKotlinMIT

At a glance

What is it?
react-native-keychain wraps the iOS Keychain and the Android Keystore for React Native apps. Everything a user needs is on a hosted documentation site; the repository README carries installation, a maintainers table and a licence line whose copyright range stopped in 2020.
Who is it for?
react-native-keychain is the boring choice for storing a token in a React Native app, and boring is the point when the alternative is writing the platform bridge yourself. Three things to check before you pick a version.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 9 days ago.
What is it written in?
Mainly Kotlin, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • oblador/react-native-keychain3,489 ★ · +10
Star history
Repository2026-09-242026-11-15
oblador/react-native-keychain3.5k3.5k

10 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The README is a pointer, not a manual

Measure this README against what it has to do and the gap is obvious. It opens with one sentence describing what the library is for, then a table of contents with six entries: installation, documentation, changelog, maintainers, used by, and licence. Five of those six sections are lists of links, a table of people, a list of three projects and a licence line. Only installation has instructions in it. Everything else is delegated, with usage documentation on a separate hosted site and the change history delegated to the releases page on the forge. For a library whose API surface is a handful of functions, that may be a defensible choice. It also means that anyone evaluating it from the repository alone is reading about four commands and a list of maintainers, and has to leave the repository to learn what the library actually does.

Installation is four steps and one is platform-specific

The installation section is a numbered list of four items. Add the package with the package manager. Run the CocoaPods install command in the iOS directory to install the iOS dependencies. Add a usage description entry for Face ID to the Info.plist file, and note that this is conditional on wanting Face ID support. Then rebuild both the Android and iOS projects. Two details are worth pausing on. The Face ID step is not part of the basic path, which means the biometric path is opt-in and its absence produces a different failure than a missing library. And the rebuild instruction at the end is doing real work: this library ships native code on both platforms, so it is a rebuild for every consumer rather than a JavaScript-only dependency that takes effect on reload.

Four entry points, and the React Native field points at source

The manifest declares four ways into the package and they do not all point at the same artefact. The main field points at a CommonJS build inside the output directory, the module field points at an ES module build in that same output, and both the React Native field and the source field point at the source directory directly. That is the standard arrangement for a native module library: a bundler in development resolves the source field and reads the JavaScript as written, while a Node consumer or a published build resolves the compiled output. The output directory itself is produced by the prepare script, which runs a builder tool, so the contents of that directory are generated rather than committed. What ships is controlled by the files array, which lists the Android directory, a single iOS subdirectory, the output directory, the source directory and the podspec.

Two type declarations, and one points outside the shipped files

There are two declarations of where the type definitions live. The standard types field points into the generated output, at the built TypeScript declaration file, while a separate TypeScript configuration block in the same manifest points at a declaration file inside a typings folder. The format script's file pattern also mentions that typings folder. Neither the typings folder nor anything else by that name appears in the repository's top level listing, so on the evidence of these files alone that declaration is either generated, ignored, or left over from an earlier layout. It is a small thing, but it is the kind of mismatch that costs an afternoon when a consumer's editor cannot find types, and it is only visible by reading the manifest rather than the documentation.

The maintainers table and the manifest list different people

The README credits one author, three maintainers and one contributor by name, with links to their profiles. The manifest lists the author with an email address and two contributors, both of whom appear in the README table as maintainers. One person named as a maintainer in the table is not in the manifest at all, which means their work is credited in the readme and nowhere else. There is also a markup slip in that table: the last row closes with an opening body tag rather than the matching closing one, which browsers tolerate and which suggests the table has been edited by hand more than once. None of this is a functional problem. It is a reminder that the credits and the manifest are maintained separately, so neither is a complete record on its own.

The copyright range stopped in 2020

The licence section is a single line: MIT, with a copyright attribution to the author and a range that ends in 2020. The release history tells a different story. The newest tag is 10.0.0 from March 2025, the one before it is a 9.x patch from February 2025, and the branch itself was pushed on 2026-04-29. So the project has shipped a major version and more than a year of commits since the year in the copyright line closed. That is the normal way an MIT notice ages, and the licence terms are unaffected. It does mean the file is not a reliable way to date the project, and if you are assembling a third party notice for a release audit, the range in the readme is a starting point rather than the answer.

Two Node pins, a markdown linter and three TypeScript configs

The root of the repository is where the tooling shows. There are two places that pin the Node version, a version manager configuration file and a version file, which is belt and braces rather than an accident. Formatting is handled by Prettier with a pattern that sweeps markdown, JavaScript, JSON and TypeScript across three directories including the example app, and linting uses a configuration file that is itself ignored by a separate ignore file. Markdown has its own linter configuration, so prose in the repository is checked by the same commit as code. There are three TypeScript configurations, one general, one for the build and one for the documentation site. Two of the directories are declared as workspaces, an example application and the website, which is also why the linter and formatter patterns reach outside the library source in the first place.

Editorial conclusion

react-native-keychain is the boring choice for storing a token in a React Native app, and boring is the point when the alternative is writing the platform bridge yourself. Three things to check before you pick a version. The usage documentation is not in the repository, so plan to read the hosted site rather than the README. The manifest declares four entry points and two separate type declarations, so check which one your bundler actually resolves rather than assuming. And the licence file carries a copyright range ending in 2020 while the newest release is from March 2025, which is harmless but worth knowing if you are assembling a third party notice.

Frequently asked questions

what is react native keychain

A React Native library that provides access to the Keychain on iOS and the Keystore on Android, for securely storing credentials such as passwords, tokens or other sensitive information in a React Native app.

how to use react native keychain

The README covers installation only: add the package, run pod install in the ios directory, add an NSFaceIDUsageDescription entry if you want Face ID support, and rebuild both platforms. Usage documentation lives on a separate documentation website rather than in the repository.

What does react-native-keychain need for Face ID?

An NSFaceIDUsageDescription entry in your Info.plist, according to the installation steps. That step is conditional: without it you do not get Face ID support, and the readme treats it as part of setup only if you want it.

Which projects use react-native-keychain?

The README names three: Rainbow Wallet, MetaMask Mobile and BlueWallet.

How is the react-native-keychain package built?

A prepare script runs a builder tool to produce the output directory, and the manifest declares four entry points: a CommonJS build, a module build, and two fields that point straight at the source. The repository has two workspaces, an example application and the documentation website.

Official sources

  1. Issues
  2. License: MIT
  3. oblador/react-native-keychain on GitHub
  4. README
  5. Releases
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/oblador-react-native-keychain.svg)](https://hysenlabs.com/projects/oblador-react-native-keychain)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/oblador-react-native-keychain.svg)](https://hysenlabs.com/projects/oblador-react-native-keychain)

Was this useful?