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

@openfort/react-native

v1.1.6

Published

React Native SDK for Openfort platform integration

Readme

Openfort React Native SDK

Quickstart sample: https://github.com/openfort-xyz/react-native-auth-sample

Usage notes

Account type and gas

The embedded wallet can be a smart account (default) or an EOA (accountType: AccountTypeEnum.EOA). Gas sponsorship (walletConfig.feeSponsorshipId) applies to smart accounts — an EOA pays its own gas in the chain's native token. Choose an EOA when it must own or sign for an external contract (e.g. a Safe), since smart-account owners require ERC-1271 contract signatures.

Wallet recovery without a backend

recoveryMethod: 'password' (or 'passkey') encrypts the key share on the client, so no Shield encryption-session backend is required. recoveryMethod: 'automatic' needs a getEncryptionSession callback (and a backend) instead.

Authentication hooks

Sign-in lives in dedicated hooks: useGuestAuth (signUpGuest), useEmailAuthOtp (requestEmailOtpsignInEmailOtp, passwordless), useEmailAuth (email + password), useOAuth, usePhoneAuthOtp, useWalletAuth, and useSignOut. A successful sign-in refreshes the session — read the user with useUser.

These methods resolve with { user?, error? }; they do not throw. Check error on the result instead of wrapping the call in try/catch:

const { requestEmailOtp, signInEmailOtp } = useEmailAuthOtp()

await requestEmailOtp({ email })
const { error } = await signInEmailOtp({ email, otp })
if (error) {
  // surface error.message — a thrown-exception handler will not catch this
}

Creating and connecting a wallet

useEmbeddedEthereumWallet().create() returns the new account but does not activate it — call setActive({ address }) afterwards to reach the connected state (with a provider). create() accepts the same recovery options as setActive().

Supported EIP-1193 methods

The embedded Ethereum provider (await wallet.getProvider()) supports, among others: eth_accounts, eth_chainId, eth_call, eth_getTransactionReceipt, eth_sendTransaction, wallet_sendCalls, personal_sign, and eth_signTypedData_v4.

Expo: reading env into app.config.js

When reading secrets from .env in app.config.js, use the function form so it merges app.json instead of replacing it (a static object drops scheme, plugins, ios, etc. and breaks expo run:ios):

// app.config.js
export default ({ config }) => ({
  ...config,
  extra: { ...config.extra, /* values from process.env */ },
})