First-party GitHub Action (action.yml) with Marketplace listing for scheduled attack-surface monitoring
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
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.
Written by the indexing model from the issue text.
Description
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 orTMHSDigital/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.
- Dominant language
- Go
- Stars
- 1
- Forks
- 1
- Avg merge
- 14d 9h
- Merged PRs (30d)
- 1
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from TMHSDigital/subenum
-
documentation testing
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
TMHSDigital/subenum#103 ·
Maintainers usually reply within 1 day
-
area: release bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
TMHSDigital/subenum#102 ·
Maintainers usually reply within 1 day
-
community marketing priority: low
Difficulty 5/5 Over a week Newbie friendliness 35/100
TMHSDigital/subenum#132 ·
Maintainers usually reply within 1 day
-
feature priority: low
Difficulty 5/5 Over a week Newbie friendliness 35/100
TMHSDigital/subenum#131 ·
Maintainers usually reply within 1 day
-
documentation marketing priority: medium
Difficulty 5/5 Over a week Newbie friendliness 25/100
TMHSDigital/subenum#127 ·
Maintainers usually reply within 1 day
All issues in TMHSDigital/subenum
Similar issues
-
[submenu] nil issue on ubuntu 26.04Possibly taken @egoist claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
prime-radiant-inc/evener#3873 ·
Maintainers usually reply within 1 day
-
extract_llm_sweep / cache_aware_summarizer prefix ask 400s when thinking.budget_tokens exceeds PrefixAskMaxTokensPossibly taken @amiddavid claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 85/100
rossoctl/context-guru#405 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
router-for-me/CLIProxyAPI#6423 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 2 days