hullabaloo-config-manager

Manages complex Babel config chains, avoiding duplicated work and enabling effective caching

hullabaloo-config-manager@1.1.1 was published on 2017-06-05. Its manifest declares 14 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=4.

All hullabaloo-config-manager versions · Permanent reference to 1.1.1

Package specifications

Version1.1.1
License declarationMIT
Published2017-06-05T10:09:57.785Z
Node.js requirement>=4
Type declarationsNot declared
Runtime dependency count14
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 entryindex.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies24
Repository stars14
Repository forks1

Install hullabaloo-config-manager 1.1.1

npm install hullabaloo-config-manager@1.1.1
pnpm add hullabaloo-config-manager@1.1.1
yarn add hullabaloo-config-manager@1.1.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.

Code-Review0/10 — Found 0/13 approved changesets -- score normalized to 0
Maintained0/10 — project is archived
Binary-Artifacts10/10 — no binaries found in the repo
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Security-Policy0/10 — security policy file not detected
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
Branch-Protection0/10 — branch protection not enabled on development/release branches
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness