Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

"Honest benchmark": reproducible comparison against puredns, shuffledns, dnsx and gobuster using lab zones

未关闭
#127 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
活跃
技术栈
go

调研方向

Start by reading the existing -simulate-zone lab mode and its scenario-directive implementation, then inspect the CLI and README/landing-page documentation entry points. The issue proposes adding bench/ scenarios and a make bench-compare script, but does not identify existing test files or benchmark infrastructure. Done means the command reproduces the published comparison table on a fresh machine and the results page is linked from the README and landing page.

由索引模型根据 Issue 内容生成。

描述

documentation marketing priority: medium

Value / who it's for

The strongest launch asset for #74. Users choosing a tool want evidence. subenum's differentiators (real rate limiting, per-query accounting, wildcard filtering, a confidence verdict) only show up in a benchmark that measures recall under adverse resolvers and queries actually sent vs the configured rate, not raw speed.

Rationale

Lab mode (-simulate-zone) with $REFUSE-ABOVE/$DELAY-style scenario directives makes a fully local, legal and reproducible benchmark possible. Competitors can be pointed at the same local server with their resolver flags.

Suggested approach

  • bench/ with scenario zones: clean, wildcard, rotating-pool wildcard, rate-limited resolver, flaky resolver, plus a script (make bench-compare) that runs each tool against the local server and records recall, false positives, wall time and wire queries (counted at the server).
  • A docs page with the results table, versions, and how to reproduce. Include where subenum loses; honesty is the brand.

Done when

make bench-compare reproduces the published table on a fresh machine, and the page is linked from the README and landing page.

主要语言
Go
星标
1
派生
1
平均合并
5 天 2 小时
30 天内合并 PR
3

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

TMHSDigital/subenum 的其他 Issue

查看 TMHSDigital/subenum 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。