composer 0.11.4
API-first task runner with three methods: task, run and watch.
composer@0.11.4 was published on 2016-04-21. Its manifest declares 11 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=4.0.
All composer versions · Permanent reference to 0.11.4 · Latest release
Package specifications
| Version | 0.11.4 |
|---|---|
| License declaration | MIT |
| Published | 2016-04-21T03:29:29.553Z |
| Node.js requirement | >=4.0 |
| Type declarations | Not declared |
| Runtime dependency count | 11 |
| 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 | 68 |
| Repository stars | 37 |
| Repository forks | 6 |
Install composer 0.11.4
npm install composer@0.11.4 pnpm add composer@0.11.4 yarn add composer@0.11.4
Runtime dependencies
- co ^4.6.0
- bach ^0.5.0
- is-glob ^2.0.1
- isobject ^2.0.0
- lazy-cache ^1.0.3
- micromatch ^2.3.7
- nanoseconds ^0.1.0
- array-unique ^0.2.1
- is-generator ^1.0.3
- define-property ^0.2.5
- component-emitter ^1.2.1
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.
- arr-diff@2.0.0 — indirect
- arr-flatten@1.1.0 — indirect
- array-unique@0.2.1 — direct
- async-done@0.4.0 — indirect
- async-done@1.3.2 — indirect
- async-settle@0.2.1 — indirect
- bach@0.5.0 — direct
- braces@1.8.5 — indirect
- co@4.6.0 — direct
- component-emitter@1.3.1 — direct
- define-property@0.2.5 — direct
- end-of-stream@0.1.5 — indirect
- end-of-stream@1.4.5 — indirect
- expand-brackets@0.1.5 — indirect
- expand-range@1.8.2 — indirect
- extglob@0.3.2 — indirect
- filename-regex@2.0.1 — indirect
- fill-range@2.2.4 — indirect
- for-in@1.0.2 — indirect
- for-own@0.1.5 — indirect
- function-bind@1.1.2 — indirect
- glob-base@0.3.0 — indirect
- glob-parent@2.0.0 — indirect
- hasown@2.0.4 — indirect
- is-accessor-descriptor@1.0.2 — indirect
- is-buffer@1.1.6 — indirect
- is-data-descriptor@1.0.1 — indirect
- is-descriptor@0.1.8 — indirect
- is-dotfile@1.0.3 — indirect
- is-equal-shallow@0.1.3 — indirect
- is-extendable@0.1.1 — indirect
- is-extglob@1.0.0 — indirect
- is-generator@1.0.3 — direct
- is-glob@2.0.1 — direct
- is-number@2.1.0 — indirect
- is-number@4.0.0 — indirect
- is-posix-bracket@0.1.1 — indirect
- is-primitive@2.0.0 — indirect
- isarray@1.0.0 — indirect
- isobject@2.1.0 — direct
- kind-of@3.2.2 — indirect
- kind-of@6.0.3 — indirect
- lazy-cache@1.0.4 — direct
- lodash.filter@4.6.0 — indirect
- lodash.flatten@4.4.0 — indirect
- lodash.foreach@4.5.0 — indirect
- lodash.initial@4.1.1 — indirect
- lodash.last@3.0.0 — indirect
- lodash.map@4.6.0 — indirect
- math-random@1.0.4 — indirect
- micromatch@2.3.11 — direct
- nanoseconds@0.1.0 — direct
- next-tick@0.2.2 — indirect
- normalize-path@2.1.1 — indirect
- now-and-later@0.0.6 — indirect
- object.omit@2.0.1 — indirect
- once@1.3.3 — indirect
- once@1.4.0 — indirect
- parse-glob@3.0.4 — indirect
- preserve@0.2.0 — indirect
- process-nextick-args@2.0.1 — indirect
- randomatic@3.1.1 — indirect
- regex-cache@0.4.4 — indirect
- remove-trailing-separator@1.1.0 — indirect
- repeat-element@1.1.4 — indirect
- repeat-string@1.6.1 — indirect
- stream-exhaust@1.0.2 — indirect
- wrappy@1.0.2 — 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.
| Code-Review | 0/10 — Found 1/20 approved changesets -- score normalized to 0 |
|---|---|
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| 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 |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 10/10 — license file detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| Security-Policy | 0/10 — security policy file not detected |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/composer/0.11.4 — retrieved 2026-10-29T23:06:14.128Z
- https://api.deps.dev/v3/projects/github.com%2Fdoowb%2Fcomposer — retrieved 2026-10-29T22:28:21.461Z
- https://api.deps.dev/v3/systems/npm/packages/composer/versions/0.11.4 — retrieved 2026-10-29T23:06:14.627Z
- https://api.deps.dev/v3/systems/npm/packages/composer/versions/0.11.4:dependencies — retrieved 2026-10-29T23:06:14.660Z