expo-symbols
npmv57.0.2TypeScriptProvides access to the SF Symbols library on iOS, and Material Symbols on Android and web, for Expo and React Native apps.
Safe to adopt
Yes — expo-symbols scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 34 days ago. 50 releases in the last 2 years.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- AMaintenance: grade A, Excellent.
Last published 34 days ago. 50 releases in the last 2 years.
- AWeight: grade A, Excellent.
Pulls in 2 transitive packages, about 7.8 MB installed.
- ASupply chain: grade A, Excellent.
No install scripts, 12 maintainers, and a contained dependency 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-symbols to a project.
Runtime packages this one declares itself.
Distinct packages in the full runtime tree, deduplicated the way a package manager would.
Unpacked size of this package plus its entire runtime tree.
Longest resolved dependency chain below this package.
Licenses in the dependency tree
Every license you inherit by installing expo-symbols, not just its own. Check this before a legal review, not after.
Compatibility
- Node.js
- No constraint declared
- Module format
- CommonJS only
- TypeScript
- Types included
- Install scripts
- None
expo-symbols vs the alternatives
Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.
| Package | Weekly downloads | Dependents | License | Last release |
|---|---|---|---|---|
| expo-symbolsthis page | 0 | 1 | MIT | 1 month ago |
| @expo/config | 9.1M | 5 | MIT | 1 day ago |
| expo-file-system | 8.4M | 1 | MIT | 1 day ago |
| @op-engineering/op-sqlite | 0 | 1 | MIT | 1 day ago |
| babel-preset-expo | 0 | 1 | MIT | 1 day ago |
| @expo/devtools | 0 | 1 | MIT | 1 day ago |
Dependencies
Declared by expo-symbols v57.0.2. Runtime dependencies are installed with the package; dev dependencies are not.
Dev (4)
Used by
Popular packages that depend on expo-symbols.
Relationship graph
Dependencies (left) and dependents (right) of expo-symbols.
Frequently installed together
Native navigation primitives for your React Native app.
Simple and complete React Native testing utilities that encourage good testing practices.
Declarative API exposing native platform touch and gesture system to React Native
React Server Components bindings for DOM using Webpack. This is intended to be integrated into meta-frameworks. It is not intended to be imported directly.
More powerful alternative to Animated library for React Native.
The Expo SDK
Tools for making advanced Metro bundler features work
Error overlay for universal Expo apps.
React Native for Web
Escape RegExp special characters
React is a JavaScript library for building user interfaces.
React package for working with the DOM.
Release history
50 releases in the last two years, typically about 2 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 58.0.0-canary-20260908-e343e6e | 1 day ago | 263 KB | MIT |
| 58.0.0-canary-20260902-26df09e | 7 days ago | 263 KB | MIT |
| 58.0.0-canary-20260901-2164f24 | 8 days ago | 263 KB | MIT |
| 58.0.0-canary-20260812-27f94d4 | 28 days ago | 263 KB | MIT |
| 58.0.0-canary-20260806-8c2d007 | 1 month ago | 263 KB | MIT |
| 56.0.7 | 1 month ago | 300 KB | MIT |
| 57.0.2latest | 1 month ago | 300 KB | MIT |
| 57.0.0-canary-20260723-64edab9 | 1 month ago | 278 KB | MIT |
| 57.0.0-canary-20260720-b6d63bc | 1 month ago | 278 KB | MIT |
| 57.0.0-canary-20260718-7cbcda5 | 1 month ago | 278 KB | MIT |
| 57.0.0-canary-20260716-381e806 | 1 month ago | 278 KB | MIT |
| 57.0.1 | 1 month ago | 300 KB | MIT |
| 56.0.6-canary-20260701-9100865 | 2 months ago | 278 KB | MIT |
| 57.0.0-canary-20260629-3010085 | 2 months ago | 278 KB | MIT |
| 56.0.6-canary-20260628-fc0d9b4 | 2 months ago | 274 KB | MIT |
Overview
expo-symbols is an npm package that provides access to the SF Symbols library on iOS, and Material Symbols on Android and web, for Expo and React Native apps. It has 1 known dependents in the graph. The latest version is 57.0.2, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need provides access to the SF Symbols library on iOS, and Material Symbols on Android and web, for Expo and React Native apps and value a focused solution.
When not to use it
Consider an alternative if you need to or if a more actively-maintained option better fits your npm stack.
Pros
- Ships TypeScript type definitions.
- Clear open-source license (MIT).
Cons
- No significant drawbacks detected from available metadata.
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Frequently asked questions
Should I use expo-symbols?
Yes — expo-symbols scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 34 days ago. 50 releases in the last 2 years.
How do I install expo-symbols?
Run `npm install expo-symbols` to add expo-symbols to your npm project.
How many dependencies does expo-symbols have?
expo-symbols declares 10 direct dependencies and pulls in 2 packages in total once its runtime tree is resolved totalling about 7.8 MB on disk.
What license is expo-symbols released under?
expo-symbols is distributed under the MIT license. Its dependency tree also includes: MIT, MIT AND Apache-2.0.
How popular is expo-symbols?
npm does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on expo-symbols.
Is expo-symbols still maintained?
The most recent release of expo-symbols (v57.0.2) was published 1 month ago.
Does expo-symbols run install scripts?
No. expo-symbols does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.