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 天內回覆