browser-launcher2 0.4.1

Detect, launch and stop browser versions

browser-launcher2@0.4.1 was published on 2014-08-08. Its manifest declares 6 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.

All browser-launcher2 versions · Permanent reference to 0.4.1 · Latest release

Package specifications

Version	0.4.1
License declaration	MIT
Published	2014-08-08T13:48:03.270Z
Node.js requirement	Not declared
Type declarations	Not declared
Runtime dependency count	6
Peer requirement count	0
Optional dependency count	0
Minified size	Measurement not available yet
Minified + gzip	Measurement not available yet
Unpacked distribution size	Not supplied
Published file count	Not supplied
Package type	Not declared
ES module entry	Not declared
Default entry	index.js
Side effects declaration	Not declared
Direct advisories	0
Resolved graph dependencies	16
Repository stars	24
Repository forks	16

Install browser-launcher2 0.4.1

npm install browser-launcher2@0.4.1
pnpm add browser-launcher2@0.4.1
yarn add browser-launcher2@0.4.1

Runtime dependencies

headless ^0.1.7
lodash ^2.4.1
mkdirp ^0.5.0
osenv ^0.1.0
plist ^1.0.1
win-detect-browsers ^0.0.2

Peer requirements

None declared

Optional dependencies

None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

base64-js@0.0.8 — indirect
headless@0.1.7 — direct
isexe@2.0.0 — indirect
lodash@2.4.2 — direct
lodash@3.10.1 — indirect
minimist@1.2.8 — indirect
mkdirp@0.5.6 — direct
os-homedir@1.0.2 — indirect
os-tmpdir@1.0.2 — indirect
osenv@0.1.5 — direct
plist@1.2.0 — direct
util-deprecate@1.0.2 — indirect
which@1.3.1 — indirect
win-detect-browsers@0.0.2 — direct
xmlbuilder@4.0.0 — indirect
xmldom@0.1.31 — indirect

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Maintained	0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Code-Review	1/10 — Found 4/27 approved changesets -- score normalized to 1
Binary-Artifacts	10/10 — no binaries found in the repo
CII-Best-Practices	0/10 — no effort to earn an OpenSSF best practices badge detected
Security-Policy	0/10 — security policy file not detected
Fuzzing	0/10 — project is not fuzzed
License	9/10 — license file detected
Branch-Protection	0/10 — branch protection not enabled on development/release branches
SAST	0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness

https://registry.npmjs.org/browser-launcher2/0.4.1 — retrieved 2026-10-30T12:28:24.162Z
https://api.deps.dev/v3/projects/github.com%2Fbenderjs%2Fbrowser-launcher2 — retrieved 2026-10-30T10:08:35.904Z
https://api.deps.dev/v3/systems/npm/packages/browser-launcher2/versions/0.4.1 — retrieved 2026-10-30T12:28:24.633Z
https://api.deps.dev/v3/systems/npm/packages/browser-launcher2/versions/0.4.1:dependencies — retrieved 2026-10-30T12:28:24.654Z