@wessberg/browserslist-generator 0.0.7

A library that helps with generating a browserslist automatically. For example, a browserslist can be generated that targets only browsers that support specific required features.

@wessberg/browserslist-generator@0.0.7 was published on 2018-05-01. Its manifest declares 3 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=9.0.0.

Deprecated: wessberg/browserslist-generator has been renamed to browserslist-generator. Please use browserslist-generator instead

All @wessberg/browserslist-generator versions · Permanent reference to 0.0.7 · Latest release

Package specifications

Version0.0.7
License declarationMIT
Published2018-05-01T22:49:44.857Z
Node.js requirement>=9.0.0
Type declarationsBundled declarations
Runtime dependency count3
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size13.32 KiB
Published file count15
Package typeNot declared
ES module entry./dist/es2015/index.js
Default entry./dist/cjs/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies21
Repository stars95
Repository forks8

Install @wessberg/browserslist-generator 0.0.7

npm install @wessberg/browserslist-generator@0.0.7
pnpm add @wessberg/browserslist-generator@0.0.7
yarn add @wessberg/browserslist-generator@0.0.7

Runtime dependencies

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.

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.

Maintained0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Binary-Artifacts10/10 — no binaries found in the repo
Code-Review0/10 — Found 0/30 approved changesets -- score normalized to 0
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
SAST0/10 — no SAST tool detected
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Fuzzing0/10 — project is not fuzzed
Security-Policy0/10 — security policy file not detected
License10/10 — license file detected
Branch-Protection0/10 — branch protection not enabled on development/release branches

Evidence and freshness