/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

remoteintech/remote-jobs

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-30T19:51:13.300Z

1mo ago

remoteintech/remote-jobs

remoteintech/remote-jobs is the source repository for remoteintech.company, a community-maintained directory of remote-friendly tech companies. It is active, popular, and content-driven rather than a general-purpose application: the repo has 40k+ stars, 3.9k forks, and recent commits on 2026-03-29. Forks are most interesting if you want to customize or repurpose a maintained static directory site built with Node.js and Eleventy.

Loading tags...

Stars40,135

Forks3,928

Default branchmain

Last pushed2026-03-29T16:43:11Z

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

Maintenance:

Magnitude:

Sort:

Selected

Choose upstream unless you explicitly need this old snapshot. For most adopters, this fork adds no benefits and carries substantial staleness risk.

Prefer upstream unless you specifically want an old, untouched snapshot. This fork does not show added capabilities and is far behind, so it is a poor choice for anyone who wants an actively maintained directory site.

Choose this fork only if you specifically want its older custom implementation and are prepared to maintain a large divergence. For most adopters, upstream is the better base because it is active, current, and much easier to extend.

Prefer upstream unless you specifically want an old snapshot. This fork has no visible added functionality and is far behind, so it is mainly useful as a static reference or a starting point for a custom rewind.

Choose this fork only if you want an old, stable snapshot to fork from. If you want a current, maintained remote-jobs directory or an up-to-date Eleventy/Node build, upstream is the better choice.

This fork is not a good choice if you want an up-to-date, maintained remote-jobs directory. It is only attractive as a dormant snapshot with no fork-specific changes to preserve.

Prefer upstream unless you specifically need this fork’s untouched historical snapshot. This fork offers no visible added capability and is far behind on upstream maintenance, so it is a poor choice for adopters who want a working, current directory site.

Choose this fork only if you specifically want an older, heavily customized baseline and are prepared to maintain it yourself. If you want an active, current directory site with intact contributor workflows, upstream is the better default.

Prefer upstream unless you want a personal, unmodified snapshot; this fork adds no clear capabilities and is substantially behind active development.

Prefer upstream unless you specifically want an archival, frozen copy. This fork has no visible enhancements and is far behind active upstream maintenance, so it is a poor choice for anyone planning to run or extend the project today.

Fork comparison

hemansnation/remote-jobs

35/100

stale

significant_divergence

Choose upstream unless you explicitly need this old snapshot. For most adopters, this fork adds no benefits and carries substantial staleness risk.

Likely purpose

A frozen copy for someone who wanted to preserve or experiment with the remote job directory at an older point in time, not a fork intended for ongoing maintenance.

Best for

People who only need an archived snapshot of the directory site.; Users studying the project history or comparing an older state against upstream.; Anyone planning a fresh fork but starting from a very old baseline for a narrow reason.

Additional features

Missing features

All upstream changes since the fork point, including the active maintenance stream.
New site features such as Carbon Ads integration and related mobile overlay fixes.
Recent content and workflow updates such as changelog link support and the newer changelog formatting.
Dependency and build updates that keep the Eleventy/Node site current and compatible.
Ongoing bug fixes and content additions merged into the upstream repo after December 2022.
It trails upstream by 828 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

No extra divergence to reconcile, so it is easy to understand as a static snapshot.
Useful if you specifically want an older copy of the project state.
Very low maintenance burden because the fork itself adds nothing new.

Risks

It is 828 commits behind upstream, so it will miss major functional, content, and dependency updates.
Adopters would inherit an old codebase with no evidence of active upkeep.
The fork does not provide any differentiated feature set, so there is little reason to choose it over upstream.
Users expecting a current remote-jobs directory will see stale data and outdated site behavior.