</>PackageGraphPackageGraph

bowser

npmv2.14.1TypeScript

Lightweight browser detector

Safe to adopt

Yes — bowser scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 213 days ago. 6 releases in the last 2 years.

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

    No download data reported for this package yet.

  • BMaintenance: grade B, Good.

    Last published 213 days ago. 6 releases in the last 2 years.

  • AWeight: grade A, Excellent.

    Zero runtime dependencies, about 252 KB installed.

  • BSupply chain: grade B, Good.

    This package has a single maintainer (bus factor of 1).

  • 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 bowser to a project.

0
Direct dependencies

Runtime packages this one declares itself.

0
Total installed

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

252 KB
Install size

Unpacked size of this package plus its entire runtime tree.

—
Tree depth

Longest resolved dependency chain below this package.

Compatibility

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

Quick start

A usage example from the bowser README.

javascriptFull README ↗
const Bowser = require("bowser"); // CommonJS

import * as Bowser from "bowser"; // TypeScript

import Bowser from "bowser"; // ES6 (and TypeScript with --esModuleInterop enabled)

bowser vs the alternatives

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

PackageWeekly downloadsDependentsLicenseLast release
bowserthis page01MIT7 months ago
plist14M2MIT1 day ago
ua-parser-js01AGPL-3.0-or-later1 day ago
commander451.1M11MIT1 day ago
postcss249.3M7MIT1 day ago
yargs-parser178.8M2ISC1 day ago

Dependencies

Declared by bowser v2.14.1. Runtime dependencies are installed with the package; dev dependencies are not.

Dev (26)

@babel/cli ^7.11.6@babel/core ^7.8.0@babel/polyfill ^7.8.3@babel/preset-env ^7.8.2@babel/register ^7.8.3ava ^3.0.0babel-eslint ^10.0.3babel-loader ^8.0.6babel-plugin-add-module-exports ^1.0.2babel-plugin-istanbul ^6.0.0compression-webpack-plugin ^4.0.0coveralls ^3.0.6docdash ^1.1.1eslint ^6.5.1eslint-config-airbnb-base ^13.2.0eslint-plugin-ava ^10.0.0eslint-plugin-import ^2.18.2gh-pages ^3.0.0jsdoc ^3.6.3nyc ^15.0.0sinon ^9.0.0testem ^3.0.0webpack ^4.41.0webpack-bundle-analyzer ^3.5.2webpack-cli ^3.3.9yamljs ^0.3.0

Used by

Popular packages that depend on bowser.

@aws-sdk/corenpm

Core functions & classes shared by multiple AWS SDK clients.

↓ 0/wk◈ 11 dependents⚖ Apache-2.0TS

Relationship graph

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

@aws-sdk/corebowser
bowser dependencies dependents

Frequently installed together

@aws-sdk/typesnpm

Types for the AWS SDK

↓ 0/wk◈ 15 dependents⚖ Apache-2.0TS
@smithy/corenpm

No description provided.

↓ 0/wk◈ 18 dependents⚖ Apache-2.0TS
@smithy/typesnpm

No description provided.

↓ 0/wk◈ 22 dependents⚖ Apache-2.0TS
@aws-sdk/xml-buildernpm

XML utilities for the AWS SDK

↓ 0/wk◈ 1 dependents⚖ Apache-2.0TS
@aws/lambda-invoke-storenpm

Invoke scoped data storage for AWS Lambda Node.js Runtime Environment

↓ 0/wk◈ 1 dependents⚖ Apache-2.0TS
@smithy/signature-v4npm

A standalone implementation of the AWS Signature V4 request signing algorithm

↓ 0/wk◈ 2 dependents⚖ Apache-2.0TS

Release history

6 releases in the last two years, typically about 22 days apart.

Recent versions of bowser
VersionPublishedSizeLicense
2.14.1latest7 months ago252 KBMIT
2.14.07 months ago707 KBMIT
2.13.19 months ago246 KBMIT
2.13.09 months ago247 KBMIT
2.12.11 year ago216 KBMIT
2.12.01 year ago216 KBMIT
2.11.06 years ago212 KBMIT
2.10.06 years ago211 KBMIT
2.9.06 years ago251 KBMIT
2.8.16 years ago251 KBMIT
2.8.06 years ago251 KBMIT
2.7.07 years ago243 KBMIT
2.6.17 years ago241 KBMIT
2.6.07 years ago241 KBMIT
2.5.47 years ago241 KBMIT

Overview

bowser is an npm package that lightweight browser detector. It has 1 known dependents in the graph. The latest version is 2.14.1, released under the MIT license.

Who should use it

Teams working in the npm ecosystem who need lightweight browser detector 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 (26 direct dependencies) increases install size and audit surface.

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

Maintainers

lancedikson

Keywords

browserdetectionenderparsersniffuauser-agentuseragent

Frequently asked questions

Should I use bowser?

Yes — bowser scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 213 days ago. 6 releases in the last 2 years.

How do I install bowser?

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

What license is bowser released under?

bowser is distributed under the MIT license.

How popular is bowser?

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

Is bowser still maintained?

The most recent release of bowser (v2.14.1) was published 7 months ago.

Does bowser run install scripts?

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