Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

First-party GitHub Action (action.yml) with Marketplace listing for scheduled attack-surface monitoring

Aberta
  • Algo errado?
#126 1 comentário 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
35/100
Tipo de issue
Funcionalidade
Clareza
Claramente especificada
Status de atividade
Ativa
Stack de tecnologia
github-actions, go
Domínio
ci-cd, security

Direção de pesquisa

Start with ROADMAP.md:24 and the existing -diff, exit-code-4, -stats, and signed-release behavior described in the issue. Define the composite Action inputs and steps in action.yml, including release verification and durable baseline storage; the issue does not name a baseline store, so that choice needs investigation. Done means a scheduled diff works with three inputs, the README and docs/monitoring.md use it, and the Action is listed on the Marketplace.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

ci feature marketing priority: medium

Value / who it's for

Security teams and bug-bounty hunters who want "tell me when a new subdomain appears" without hand-maintaining a workflow. The Marketplace is a discovery channel none of the main DNS brute-force tools (puredns, shuffledns, dnsx, gobuster) occupy. It also replaces the hand-copied example in docs/monitoring.md, which has the supply-chain and baseline problems tracked separately.

Rationale

-diff, the exit code 4 on change, the -stats verdict and signed releases with attestations already exist. An Action is mostly packaging. ROADMAP.md:24 already lists it.

Suggested approach

  • action.yml (composite) in this repo or TMHSDigital/subenum-action. Inputs: domain/domains-file, wordlist, rate, max-queries, resolvers, fail-on: degraded|unreliable, open-issue: true.
  • Steps: download the release asset for the runner OS, verify the checksum or attestation, restore the baseline from a durable store, run with -diff -stats, upload artifacts, write a job summary table, and optionally open or update an issue.
  • Publish to the Marketplace and tag v1.

Done when

uses: TMHSDigital/subenum@v1 with three inputs runs a scheduled diff end to end, the README and docs/monitoring.md use it, and it's listed on the Marketplace.

Linguagem predominante
Go
Estrelas
1
Forks
1
Merge médio
5d 2h
PRs com merge (30d)
3

Preparar o ambiente

Abrir no Codespaces

Inicia o contêiner de desenvolvimento do projeto no navegador, com a sua própria conta do GitHub.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de TMHSDigital/subenum

Todas as issues de TMHSDigital/subenum

Issues semelhantes

Mais issues de Go

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.