/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

nektos/act

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-30T12:10:02.684Z

3mo ago

nektos/act

`nektos/act` is a large, active Go project for running GitHub Actions locally. It has strong adoption (69,620 stars, 1,895 forks), is not archived, and was updated recently on 2026-03-30. The repo focuses on local workflow execution via Docker and is documented as a way to get faster feedback and use GitHub Actions as a local task runner.

Loading tags...

Stars69,620

Forks1,895

Default branchmaster

Last pushed2026-03-26T21:03: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

Maintenance:

Magnitude:

Sort:

Selected

Choose this fork only if you want a narrower distribution-oriented `act` and can tolerate losing upstream freshness and some bundled validation assets. If you want the most compatible, actively evolving local GitHub Actions runner, upstream is the safer default.

Prefer upstream unless you specifically need this fork's compatibility patches or host/runtime customizations. Choose the fork if your blocker is one of its added workflows or platform fixes; otherwise the upstream project is the safer default.

Prefer upstream `nektos/act` unless you specifically need this exact stale snapshot; this fork adds no visible value and is materially behind current upstream.

Prefer upstream unless you specifically need a stripped-down fork to build on. This fork looks less like a maintained alternative and more like an old, heavily pruned snapshot, so it is a poor choice for adopters who want current GitHub Actions compatibility.

Choose this fork only if you specifically need this frozen snapshot; otherwise upstream nektos/act is the better default because it is active and substantially ahead.

Prefer upstream for normal use. Pick this fork only if you need a frozen 2022-era `act` variant with its older compatibility patches and are willing to accept major maintenance lag.

Prefer upstream unless you specifically need a private mirror or controlled fork point; this fork does not add observable capabilities and is behind current upstream.

Prefer upstream unless you specifically need this older snapshot or its bundled test/runtime fixtures. For normal adoption, this fork looks too stale and divergent to be a better default than `nektos/act`.

Prefer this fork only if you specifically need its added offline/remote-action workflows or its rootless fixes. For most adopters, the active upstream is the safer choice because this fork is stale and materially behind.

Choose this fork only if offline mode, the newer action cache option, or NetBSD support are the main requirements. If you want current `act` behavior, security fixes, and ongoing compatibility work, upstream is the better default.

Fork comparison

xing/act

54/100

slowing

significant_divergence

Choose this fork only if you want a narrower distribution-oriented `act` and can tolerate losing upstream freshness and some bundled validation assets. If you want the most compatible, actively evolving local GitHub Actions runner, upstream is the safer default.

Likely purpose

A heavily customized downstream distribution of `act` that appears to prune a large amount of bundled test/vendor content and keep a narrower fork for local GitHub Actions execution.

Best for

Teams that want a slimmer, downstream-maintained `act` distribution rather than the full upstream repository.; Operators who only need core local workflow execution and are comfortable trading away upstream breadth and coverage.; Maintainers who package or embed `act` and prefer a trimmed fork over a fast-moving upstream.

Additional features

A distribution-focused branch that likely trims repository baggage for a lighter downstream build or packaging workflow.
Potentially easier to vendor or mirror as an internal fork because the history shows repeated submodule-style updates and a dedicated `distribution` branch.
Expands API, schema, or SDK surface area for downstream integrations and generated clients.
Adds plugin, tool, or MCP-style extensibility beyond the upstream baseline.
Changes agent workflow behavior, such as prompt handling, handoffs, worktrees, memory, or orchestration flow.
Adds performance-oriented execution paths, caching, or faster runtime modes.

Missing features

It appears far behind upstream and materially diverged, so adopters should expect missing or outdated upstream fixes and features.
Large amounts of test and bundled Node action fixture content are removed, which can make validation of runner behavior harder and reduce coverage for embedded action workflows.
Upstream’s active release and dependency-update cadence is not reflected here, so newer compatibility fixes may be absent.
It trails upstream by 200 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Still tracks the same core goal as upstream: running GitHub Actions locally.
Recent pushes suggest the fork is not abandoned and may be maintained for a specific downstream use case.
The `distribution` branch suggests a packaging-oriented variant rather than a generic experimental rewrite.

Risks

Very large file churn with massive deletions means the fork may omit important fixtures or support assets.
High divergence from upstream increases merge and maintenance burden.
Users depending on upstream’s current bugfixes, workflow compatibility, or test coverage may hit regressions.

nektos/act · Discofork