</>PackageGraphPackageGraph

expo

npmv57.0.21TypeScript

The Expo SDK

Not recommended for new projects

No — expo should not be adopted for new projects. Pulls in 341 transitive packages, about 139 MB installed (at least — some of the tree is still being crawled). This package exposes a 341-package audit surface.

  • ?Adoption: grade ?, Not reported by this registry.

    No download data reported for this package yet.

  • AMaintenance: grade A, Excellent.

    Last published 1 days ago. 50 releases in the last 2 years.

  • FWeight: grade F, Failing.

    Pulls in 341 transitive packages, about 139 MB installed (at least — some of the tree is still being crawled).

  • CSupply chain: grade C, Fair — worth a look.

    This package exposes a 341-package audit surface.

  • ALicense: grade A, Excellent.

    MIT — permissive, with no copyleft found in the dependency tree.

Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.

Install cost

What you actually take on by adding expo to a project.

23
Direct dependencies

Runtime packages this one declares itself.

341
Total installed

Distinct packages in the full runtime tree, deduplicated the way a package manager would.

139 MB
Install size

Unpacked size of this package plus its entire runtime tree.

6
Tree depth

Longest resolved dependency chain below this package.

Part of this dependency tree has not been crawled yet, so these figures are a lower bound rather than a final total.

Licenses in the dependency tree

(BSD-3-Clause OR GPL-2.0)(MIT OR Apache-2.0)(MIT OR CC0-1.0)0BSDApache-2.0BSD-2-ClauseBSD-3-ClauseBlueOak-1.0.0CC-BY-4.0ISCMITMPL-2.0

Every license you inherit by installing expo, not just its own. Check this before a legal review, not after.

Compatibility

Node.js
No constraint declared
Module format
ESM + CommonJS
TypeScript
Types included
Install scripts
None

expo vs the alternatives

Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.

PackageWeekly downloadsDependentsLicenseLast release
expothis page018MIT1 day ago
@expo/config9.1M5MIT18 hours ago
expo-file-system8.4M1MIT16 hours ago
@expo/config-plugins05MIT17 hours ago
@expo/metro-config03MIT17 hours ago
@expo/local-build-cache-provider01MIT15 hours ago

Dependencies

Declared by expo v57.0.21. Runtime dependencies are installed with the package; dev dependencies are not.

Used by

Popular packages that depend on expo.

expo-file-systemnpm

Provides access to the local file system on the device.

8.4M/wk1 dependentsMITTS
@expo/metro-confignpm

A Metro config for running React Native projects with the Metro bundler

0/wk3 dependentsMITTS
@expo/clinpm

The Expo CLI

0/wk2 dependentsMIT
@expo/log-boxnpm

Error overlay for universal Expo apps.

0/wk4 dependentsMIT
expo-constantsnpm

Provides system information that remains constant throughout the lifetime of your app.

0/wk6 dependentsMITTS
babel-preset-exponpm

The Babel preset for Expo projects

0/wk1 dependentsMITTS
expo-keep-awakenpm

Provides a React component that prevents the screen sleeping when rendered. It also exposes static methods to control the behavior imperatively.

0/wk1 dependentsMITTS
expo-fontnpm

Load fonts at runtime and use them in React Native components.

0/wk3 dependentsMITTS
@expo/dom-webviewnpm

A WebView specifically designed for Expo DOM components

0/wk2 dependentsMITTS
@expo/fingerprintnpm

A library to generate a fingerprint from a React Native project

0/wk2 dependentsMITTS
expo-assetnpm

An Expo universal module to download assets and pass them into other APIs

0/wk1 dependentsMITTS
@expo/metro-runtimenpm

Tools for making advanced Metro bundler features work

0/wk3 dependentsMITTS
@expo/router-servernpm

Expo Router is a file-based router for React Native and web applications.

0/wk1 dependentsMITTS
expo-routernpm

Expo Router is a file-based router for React Native and web applications.

0/wk2 dependentsMITTS
expo-widgetsnpm

Widgets.

0/wk1 dependentsMITTS
expo-glass-effectnpm

A component that renders a native glass effect view on iOS.

0/wk1 dependentsMITTS
expo-sqlitenpm

Provides access to a database using SQLite (https://www.sqlite.org/). The database is persisted across restarts of your app.

0/wk1 dependentsMITTS
expo-symbolsnpm

Provides access to the SF Symbols library on iOS, and Material Symbols on Android and web, for Expo and React Native apps.

0/wk1 dependentsMITTS

Relationship graph

Dependencies (left) and dependents (right) of expo.

Frequently installed together

Release history

50 releases in the last two years, typically about 2 days apart.

Recent versions of expo
VersionPublishedSizeLicense
58.0.0-canary-20260909-ea7a89a21 hours ago1.2 MBMIT
57.0.21latest1 day ago900 KBMIT
57.0.205 days ago900 KBMIT
58.0.0-canary-20260902-26df09e7 days ago1.2 MBMIT
57.0.198 days ago900 KBMIT
55.0.319 days ago860 KBMIT
57.0.1812 days ago900 KBMIT
56.0.2112 days ago886 KBMIT
57.0.1714 days ago900 KBMIT
55.0.3015 days ago860 KBMIT
57.0.1616 days ago900 KBMIT
57.0.1520 days ago900 KBMIT
54.0.3723 days ago855 KBMIT
55.0.2923 days ago860 KBMIT
56.0.2023 days ago886 KBMIT

Overview

expo is an npm package that the Expo SDK. It has 18 known dependents in the graph. The latest version is 57.0.21, released under the MIT license.

Who should use it

Teams working in the npm ecosystem who need the Expo SDK and value a focused solution.

When not to use it

Consider an alternative if you need to minimize your dependency tree, or if a more actively-maintained option better fits your npm stack.

Pros

  • Ships TypeScript type definitions.
  • Clear open-source license (MIT).

Cons

  • Large dependency tree (41 direct dependencies) increases install size and audit surface.

Auto-generated from collected registry metadata. No external claims are inferred.

Maintainers

Keywords

Frequently asked questions

Should I use expo?

No — expo should not be adopted for new projects. Pulls in 341 transitive packages, about 139 MB installed (at least — some of the tree is still being crawled). This package exposes a 341-package audit surface.

How do I install expo?

Run `npm install expo` to add expo to your npm project.

How many dependencies does expo have?

expo declares 41 direct dependencies and pulls in 341 packages in total once its runtime tree is resolved totalling about 139 MB on disk.

What license is expo released under?

expo is distributed under the MIT license. Its dependency tree also includes: (BSD-3-Clause OR GPL-2.0), (MIT OR Apache-2.0), (MIT OR CC0-1.0), 0BSD, Apache-2.0, BSD-2-Clause, BSD-3-Clause, BlueOak-1.0.0, CC-BY-4.0, ISC, MIT, MPL-2.0.

How popular is expo?

npm does not publish download counts. Within PackageGraph's crawl, 18 known packages depend on expo.

Is expo still maintained?

The most recent release of expo (v57.0.21) was published 1 day ago.

Does expo run install scripts?

No. expo does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.