Record which source (wordlist, ct, wayback, axfr, permute) found each name
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start with the Result struct in internal/output/writer.go (around lines 56-65), where the only provenance field today is Permutation bool, then look at SourceSummary in internal/output/summary.go and the summary code in main_summary.go (around lines 39-41). Trace how main_session.go passes each source's results through, so a sources list can be attached to each result. Done means JSON, JSONL and CSV output carry a sources list and SourceSummary gains a per-source found count; check with go test ./internal/output/ and go test .. The open question on multi-source labelling and text output needs a maintainer decision first.
由索引模型根据 Issue 内容生成。
描述
Summary
Results don't say where a name came from. The only provenance field is Permutation bool, and the summary counts names proposed per source, not how many resolved.
Where
internal/output/writer.go:56-65(Result)main_summary.go:39-41,internal/output/summary.go(SourceSummary)
Proposal
- Add
sources: ["wordlist","ct","wayback","axfr","permute"]to each result in JSON, JSONL and CSV. - Add a
foundcount per source toSourceSummary.
Who benefits
Users who want to know whether ct or wayback earns its requests, and which names came only from the archive. It also helps tune wordlists.
Open questions
- How to label names that come from several sources (a list, as above), and whether text output shows it.
Getting started
- Relevant files:
internal/output/writer.go,internal/output/summary.go,main_session.go - How to run tests:
go test ./internal/output/ . - Related docs:
README.md(output formats)
Filed by repo-audit/full-audit at 3f671b2. Severity: medium. Effort: M. audit-key: enhancement|internal/output/writer.go|provenance
- 主要语言
- Go
- 星标
- 1
- 派生
- 1
- 平均合并
- 7 小时 48 分钟
- 30 天内合并 PR
- 6
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
TMHSDigital/subenum 的其他 Issue
-
enhancement good first issue severity: low
难度 2/5 1-3 小时 新手友好度 62/100
TMHSDigital/subenum#275 ·
维护者通常 1 天内回复
-
good first issue severity: low testing
难度 2/5 1-3 小时 新手友好度 75/100
TMHSDigital/subenum#260 ·
维护者通常 1 天内回复
-
community documentation good first issue
难度 2/5 1-3 小时 新手友好度 85/100
TMHSDigital/subenum#135 ·
维护者通常 1 天内回复
-
severity: medium tech-debt
难度 4/5 3-5 天 新手友好度 35/100
TMHSDigital/subenum#277 ·
维护者通常 1 天内回复
-
enhancement help wanted severity: medium
难度 3/5 1-2 天 新手友好度 55/100
TMHSDigital/subenum#274 ·
维护者通常 1 天内回复
查看 TMHSDigital/subenum 的全部 Issue
相似的 Issue
-
area: interop area: sip-core v3
难度 2/5 1-3 小时 新手友好度 62/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
deadfin-org/deadfin#35 ·
-
enhancement
难度 2/5 1-3 小时 新手友好度 66/100
-
enhancement priority: low
难度 2/5 1-3 小时 新手友好度 72/100
labmonkeys-space/nl6#1037 ·
维护者通常 1 天内回复
-
Setup Guide Go tab: say it needs Go 1.26 (the unversioned go get pulls OpenTelemetry Go v1.47.0)未关闭enhancement follow-up
难度 2/5 1-3 小时 新手友好度 66/100
维护者通常 1 天内回复