Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Ship on package managers: Homebrew tap, Scoop bucket, AUR, Nix, and Kali/BlackArch

Open
#62 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
go
Domain
cli, release

Research direction

Start by reading the GoReleaser configuration and README, then check the project’s release workflow to see how releases are currently published. The issue calls for Homebrew and Scoop installs to work and be documented, with AUR and nixpkgs submissions open; distro inclusion requests are explicitly deferred until a stable 1.0 and some usage.

Written by the indexing model from the issue text.

Description

area: release enhancement marketing priority: medium

Why it matters

Pentesters install tools via brew, scoop, yay, nix or their distro (Kali, BlackArch, Parrot), not by downloading binaries from GitHub. Right now the only routes are go install, release downloads and GHCR. Distro packaging is also the strongest discovery channel for recon tools.

Suggested approach

  • With GoReleaser in place, add brews: (tap TMHSDigital/homebrew-tap) and scoops: (bucket repo). These are generated on every release.
  • AUR: a subenum-bin PKGBUILD, generated by GoReleaser's aurs: or maintained by hand.
  • Nix: a PR to nixpkgs (buildGoModule).
  • Kali/BlackArch: file a tool-inclusion request once there is a stable 1.0 and some usage. BlackArch accepts PRs directly.
  • Add an "Install" matrix to the README and the site.

Done when

brew install TMHSDigital/tap/subenum and scoop install subenum work and are documented, with AUR and nixpkgs submissions open.

Dominant language
Go
Stars
1
Forks
1
Avg merge
5d 2h
Merged PRs (30d)
3

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from TMHSDigital/subenum

All issues in TMHSDigital/subenum

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.