Discofork
Repository brief

gkd-kit/gkd

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-30T20:01:20.058Z
1mo ago

gkd-kit/gkd

`gkd-kit/gkd` is a popular, actively maintained Android app for custom screen tapping built around Accessibility, advanced selectors, and subscription-based rules. It is GPL-3.0 licensed, has a large user/developer base, and the repo looks actively developed with recent fixes and feature work as of 2026-03-30.

GitHub
Loading tags...
Stars37,413
Forks1,798
Default branchmain
Last pushed2026-03-30T14:01:21Z
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

Choose this fork if you want a more opinionated GKD with extra management workflows and can accept drift from upstream. Choose upstream if you want the latest fixes, better compatibility, and the standard rule-management experience.

Adopt this fork only if you specifically want a clean upstream snapshot. For day-to-day use, upstream is the better choice because this fork is already 23 commits behind and adds nothing of its own.

Choose this fork only if you want a strongly customized, older baseline and are prepared to own maintenance. If you want the latest upstream features, fixes, and compatibility work, upstream is the better fit.

Choose this fork only if you want its custom workflow and are comfortable living with a stale, heavily diverged codebase. If you want the latest fixes, Android compatibility, and lower maintenance risk, upstream is the safer choice.

Choose this fork only if you want its added permissions, subscription-management changes, and custom workflow tweaks, and you are willing to inherit a stale, heavily diverged codebase. If you want current compatibility and lower maintenance risk, upstream is the safer choice.

Choose this fork only if you specifically need its older customized behavior or rule-priority changes. For most adopters, upstream is the safer choice because this fork is stale and far behind on fixes and ongoing feature work.

Choose this fork if you want a more opinionated GKD variant with extra config, subscription, and packaging workflows. Avoid it if you want current upstream fixes, platform compatibility work, and easier long-term maintenance.

Choose this fork only if its added backup/subscription workflows match a specific need and you are comfortable maintaining a significantly outdated codebase. For most users, upstream is the better default because this fork is materially stale and likely missing many recent fixes and improvements.

Choose this fork only if its older selector/snapshot workflow is specifically what you need. For most adopters, upstream is the safer default because this fork is stale, materially behind, and likely missing newer fixes and compatibility work.

Choose this fork if live update notifications are the main thing you want and you can accept being materially behind upstream. If you want the latest fixes, device compatibility work, and broader feature progress, upstream is the safer choice.