Discofork
Repository brief

gulpjs/gulp

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-31T10:15:11.107Z
1mo ago

gulpjs/gulp

gulpjs/gulp is the core gulp build-system repository: a Node.js/JavaScript toolkit for automating workflow tasks, with a minimal API, CLI support, and both CommonJS and ESM entry points. It is active, not archived, and has recent commits through 2026-02-09. The project is mature and widely used, with 32,997 stars and 4,175 forks.

GitHub
Loading tags...
Stars32,997
Forks4,175
Default branchmaster
Last pushed2026-02-09T06:30:13Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Prefer upstream unless you specifically need this fork's older task/CLI behavior. This fork looks stale and materially behind current gulp, so it is a compatibility choice, not a modern default.

Prefer upstream unless you specifically need this tiny docs-only fork; it offers almost no extra capability and is materially stale.

Prefer upstream unless you specifically need the fork's legacy CLI/workflow customizations and are prepared to maintain a frozen, outdated codebase. This fork looks useful for legacy preservation, not for new adoption.

Prefer upstream unless you specifically need this fork's exact frozen state; it adds no visible capabilities and is behind on maintenance.

Choose this fork only if you need legacy gulp behavior exactly as preserved here. For new work or active projects, upstream is the safer choice because this fork is far behind and missing modern support and fixes.

Choose this fork if you need a maintained, customized gulp line and can absorb divergence risk. Choose upstream if you want the broadest compatibility, latest fixes, and the least maintenance overhead.

Prefer upstream unless you need a static snapshot of gulp at the fork point; this fork adds nothing and is behind on useful maintenance fixes.

Prefer upstream unless you specifically need the WhiteSource config; this fork adds one operational feature but is materially outdated and offers little else for most adopters.

Choose this fork only if you need a sustained gulp v3 compatibility branch. If you want current gulp behavior, active maintenance, and modern Node support, upstream is the better choice.

Choose upstream unless you specifically need this older, unchanged snapshot. The fork adds no visible features and is behind on recent fixes and compatibility updates.