Project
Roadmap
Where subenum is going next. Everything that has shipped is in the CHANGELOG; this page only lists open work. Each item links to its issue, which is the place to discuss it or offer help.
Now
Work in progress or next up.
- GitHub Marketplace listing for the subenum Action (#126), now that v0.9.0 ships the release archives it installs.
Next
Planned features that make results more trustworthy and the tool easier to get.
- Package managers (#62): Homebrew, Scoop, AUR, Nix, Kali/BlackArch.
- A reproducible benchmark against other DNS brute-forcers on lab zones (#127).
Later
Ideas we want, with no date attached.
- Discoverability: demo GIF and launch posts (#74), and MCP registry listings for
subenum mcp.
What 1.0 means
subenum reaches 1.0 when scripts and pipelines can depend on it without surprises:
- Stable flags. No flag is renamed or removed without a deprecation release
first (as
-retrieswas for-attempts). - Stable output schemas. The JSON, JSONL and CSV fields are documented and only ever gain fields, never lose or rename them. The field reference and its JSON Schema files are in place, and a test keeps them in step with the code.
- Documented exit codes, already in place (0, 1, 2, 3, 4, 130, 143).
- A run-quality report, already in place (
-stats, schema 1), so a result set says how far it can be trusted. - Verifiable releases, in place since v0.9.0: checksums, SBOMs, cosign signatures and provenance attestations.
- A stable library API.
pkg/subenumfollows semantic versioning from 1.0; until then it may change between minor releases.
Known limitations
Constraints to keep in mind when changing the code.
- The test DNS server (
internal/dnstest) models A, AAAA, CNAME, NS, MX, TXT, SRV, HTTPS and PTR answers, AXFR, NSEC records in the authority section and referrals (NS records in the authority section, told apart by the query’s RD bit), any RCODE, NODATA with SOA, delays, drops and truncation (scripted, or when a UDP answer exceeds the query’s EDNS buffer). Other record types are not modelled; extendReplyininternal/dnsserver(whichinternal/dnstestre-exports) before testing them. - DNS goes through Go’s stdlib resolver. Its internal retries depend on the
host’s resolver configuration.
-ratecharges every query it dials, but the number of queries per lookup is not fully under subenum’s control. - The reliability guard is tested with injected timeouts, not simulate misses, because simulate misses classify as NXDOMAIN, which is excluded from the failure rate by design.
- The
godirective is pinned at1.26.0and CI checks it. New dependencies must keep it and passgovulncheckin CI. On PowerShell, quote-go=1.26.0; unquoted it is parsed as-go=1.