Record which source (wordlist, ct, wayback, axfr, permute) found each name

Abierto
  • ¿Algo no está bien?
#273 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
55/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
go
Área
cli

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement help wanted severity: medium

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 found count per source to SourceSummary.

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

Lenguaje dominante
Go
Estrellas
1
Forks
1
Merge medio
7 h 48 min
PR fusionados (30 d)
6

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de TMHSDigital/subenum

Todos los issues de TMHSDigital/subenum

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.