expo-linking
npmv57.0.9TypeScriptCreate and open deep links universally
Safe to adopt
Yes — expo-linking scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 8 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 8 days ago. 50 releases in the last 2 years.
- BWeight: grade B, Good.
Pulls in 9 transitive packages, about 456 KB installed (at least — some of the tree is still being crawled).
- ASupply chain: grade A, Excellent.
No install scripts, 13 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-linking 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.
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
Every license you inherit by installing expo-linking, 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-linking 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-linkingthis page | 0 | 1 | MIT | 8 days ago |
| @expo/config | 9.1M | 5 | MIT | 1 day ago |
| expo-file-system | 8.4M | 1 | MIT | 1 day ago |
| expo-font | 0 | 3 | MIT | 1 day ago |
| expo-keep-awake | 0 | 1 | MIT | 1 day ago |
| expo-constants | 0 | 6 | MIT | 1 day ago |
Dependencies
Declared by expo-linking v57.0.9. Runtime dependencies are installed with the package; dev dependencies are not.
Runtime (2)
Peer (2)
Dev (3)
Used by
Popular packages that depend on expo-linking.
Relationship graph
Dependencies (left) and dependents (right) of expo-linking.
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 | 132 KB | MIT |
| 58.0.0-canary-20260902-26df09e | 7 days ago | 132 KB | MIT |
| 58.0.0-canary-20260901-2164f24 | 8 days ago | 132 KB | MIT |
| 57.0.9latest | 8 days ago | 166 KB | MIT |
| 57.0.8 | 14 days ago | 166 KB | MIT |
| 57.0.7 | 20 days ago | 166 KB | MIT |
| 55.0.17 | 23 days ago | 162 KB | MIT |
| 56.0.17 | 23 days ago | 166 KB | MIT |
| 57.0.6 | 26 days ago | 166 KB | MIT |
| 58.0.0-canary-20260812-27f94d4 | 28 days ago | 133 KB | MIT |
| 58.0.0-canary-20260806-8c2d007 | 1 month ago | 133 KB | MIT |
| 57.0.5 | 1 month ago | 166 KB | MIT |
| 57.0.0-canary-20260723-64edab9 | 1 month ago | 129 KB | MIT |
| 56.0.16 | 1 month ago | 166 KB | MIT |
| 57.0.4 | 1 month ago | 166 KB | MIT |
Overview
expo-linking is an npm package that create and open deep links universally. It has 1 known dependents in the graph. The latest version is 57.0.9, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need create and open deep links universally 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
Keywords
Frequently asked questions
Should I use expo-linking?
Yes — expo-linking scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 8 days ago. 50 releases in the last 2 years.
How do I install expo-linking?
Run `npm install expo-linking` to add expo-linking to your npm project.
How many dependencies does expo-linking have?
expo-linking declares 7 direct dependencies and pulls in 9 packages in total once its runtime tree is resolved totalling about 456 KB on disk.
What license is expo-linking released under?
expo-linking is distributed under the MIT license.
How popular is expo-linking?
npm does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on expo-linking.
Is expo-linking still maintained?
The most recent release of expo-linking (v57.0.9) was published 8 days ago.
Does expo-linking run install scripts?
No. expo-linking does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.