ua-parser-js
npmv2.0.10TypeScriptDetect Browser, Engine, OS, CPU, and Device type/model from User-Agent & Client Hints data. Supports browser & node.js environment
Adopt with care
ua-parser-js is usable, with caveats. AGPL-3.0-or-later is a strong copyleft license — it can impose obligations on your own code.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- BMaintenance: grade B, Good.
Last published 112 days ago. 20 releases in the last 2 years.
- AWeight: grade A, Excellent.
Pulls in 3 transitive packages, about 1.3 MB installed.
- BSupply chain: grade B, Good.
This package has a single maintainer (bus factor of 1).
- DLicense: grade D, Poor — a real concern.
AGPL-3.0-or-later is a strong copyleft license — it can impose obligations on your own code.
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 ua-parser-js 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 ua-parser-js, not just its own. Check this before a legal review, not after.
Compatibility
- Node.js
- node *
- Module format
- ESM + CommonJS
- TypeScript
- Types included
- Install scripts
- None
ua-parser-js 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 |
|---|---|---|---|---|
| ua-parser-jsthis page | 0 | 1 | AGPL-3.0-or-later | 3 months ago |
| ua-is-frozen | 0 | 1 | MIT | 1 day ago |
| bowser | 0 | 1 | MIT | 1 day ago |
| isarray | 174.9M | 3 | MIT | 1 day ago |
| open | 130.4M | 4 | MIT | 1 day ago |
| axios | 106.5M | 4 | MIT | 1 day ago |
Dependencies
Declared by ua-parser-js v2.0.10. Runtime dependencies are installed with the package; dev dependencies are not.
Dev (13)
Used by
Popular packages that depend on ua-parser-js.
Relationship graph
Dependencies (left) and dependents (right) of ua-parser-js.
Frequently installed together
Fast (and loose) selective `process.env` replacer using js-tokens instead of an AST
A shim for the setImmediate efficient script yielding API
Universal WHATWG Fetch API for Node, Browsers and React Native
This package exports a few of the CSS variables that we use in Facebook projects. This is not the full list we have internally but focused on making available the minimum set needed by our open source projects.
Bare bones Promises/A+ implementation
Immutable Data Collections
Create a stream that emits events from multiple other streams
Delightful JavaScript Testing.
Release history
14 releases in the last two years, typically about 31 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 2.0.10latest | 3 months ago | 1.3 MB | AGPL-3.0-or-later |
| 2.0.9 | 7 months ago | 1.2 MB | AGPL-3.0-or-later |
| 2.0.8 | 7 months ago | 468 KB | AGPL-3.0-or-later |
| 2.0.7 | 9 months ago | 1.2 MB | AGPL-3.0-or-later |
| 2.0.6 | 11 months ago | 1.2 MB | AGPL-3.0-or-later |
| 2.0.5 | 1 year ago | 1.2 MB | AGPL-3.0-or-later |
| 1.0.41 | 1 year ago | 122 KB | MIT |
| 0.7.41 | 1 year ago | 122 KB | MIT |
| 2.0.4 | 1 year ago | 1.2 MB | AGPL-3.0-or-later |
| 2.0.3 | 1 year ago | 1.2 MB | AGPL-3.0-or-later |
| 2.0.2 | 1 year ago | 1.1 MB | AGPL-3.0-or-later |
| 2.0.1 | 1 year ago | 1.1 MB | AGPL-3.0-or-later |
| 1.0.40 | 1 year ago | 116 KB | MIT |
| 0.7.40 | 1 year ago | 116 KB | MIT |
| 2.0.0 | 1 year ago | 1.1 MB | AGPL-3.0-or-later |
Overview
ua-parser-js is an npm package that detect Browser, Engine, OS, CPU, and Device type/model from User-Agent & Client Hints data. Supports browser & node.js environment. It has 1 known dependents in the graph. The latest version is 2.0.10, released under the AGPL-3.0-or-later license.
Who should use it
Teams working in the npm ecosystem who need detect Browser, Engine, OS, CPU, and Device type/model from User-Agent & Client Hints data. Supports browser & node.js environment 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 (AGPL-3.0-or-later).
Cons
- Large dependency tree (16 direct dependencies) increases install size and audit surface.
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Funding
Frequently asked questions
Should I use ua-parser-js?
ua-parser-js is usable, with caveats. AGPL-3.0-or-later is a strong copyleft license — it can impose obligations on your own code.
How do I install ua-parser-js?
Run `npm install ua-parser-js` to add ua-parser-js to your npm project.
How many dependencies does ua-parser-js have?
ua-parser-js declares 16 direct dependencies and pulls in 3 packages in total once its runtime tree is resolved totalling about 1.3 MB on disk.
What license is ua-parser-js released under?
ua-parser-js is distributed under the AGPL-3.0-or-later license.
How popular is ua-parser-js?
npm does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on ua-parser-js.
Is ua-parser-js still maintained?
The most recent release of ua-parser-js (v2.0.10) was published 3 months ago.
Does ua-parser-js run install scripts?
No. ua-parser-js does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.