buster-configuration

Groks the buster.js configuration file, including resource loading, file globbing, grouped test configs and more

buster-configuration@0.8.1 was published on 2015-11-25. Its manifest declares 6 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >= 4.

Deprecated: No longer maintained

All buster-configuration versions · Permanent reference to 0.8.1

Package specifications

Version0.8.1
License declarationBSD-3-Clause
Published2015-11-25T22:54:44.938Z
Node.js requirement>= 4
Type declarationsNot declared
Runtime dependency count6
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution sizeNot supplied
Published file countNot supplied
Package typeNot declared
ES module entryNot declared
Default entry./lib/buster-configuration
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies16
Repository stars2
Repository forks2

Install buster-configuration 0.8.1

npm install buster-configuration@0.8.1
pnpm add buster-configuration@0.8.1
yarn add buster-configuration@0.8.1

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 — project is archived
Code-Review0/10 — Found 1/25 approved changesets -- score normalized to 0
Binary-Artifacts10/10 — no binaries found in the repo
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
License9/10 — license file detected
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0
Branch-Protection0/10 — branch protection not enabled on development/release branches

Evidence and freshness