First-party GitHub Action (action.yml) with Marketplace listing for scheduled attack-surface monitoring
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 5/5
- 預估耗時
- 一週以上
- 新手友好度
- 35/100
研究方向
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.
由索引模型根據 Issue 內容生成。
描述
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.
- 主要語言
- Go
- 星號
- 1
- 分支
- 1
- 平均合併
- 5 天 2 小時
- 30 天內合併 PR
- 3
環境準備
在瀏覽器裡用你自己的 GitHub 帳號啟動這個專案的開發容器。
- 提供 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
TMHSDigital/subenum 的其他 Issue
-
area: cli enhancement good first issue
難度 2/5 1-3 小時 新手友好度 88/100
TMHSDigital/subenum#136 ·
維護者通常 1 天內回覆
-
community documentation good first issue
難度 2/5 1-3 小時 新手友好度 85/100
TMHSDigital/subenum#135 ·
維護者通常 1 天內回覆
-
area: dns enhancement good first issue
難度 2/5 1 小時以內 新手友好度 90/100
TMHSDigital/subenum#134 ·
維護者通常 1 天內回覆
-
community marketing priority: low
難度 5/5 一週以上 新手友好度 35/100
TMHSDigital/subenum#132 · 1 則留言 ·
維護者通常 1 天內回覆
-
feature priority: low
難度 5/5 一週以上 新手友好度 35/100
TMHSDigital/subenum#131 ·
維護者通常 1 天內回覆
查看 TMHSDigital/subenum 的全部 Issue
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 78/100
維護者通常 1 天內回覆
-
duplication
難度 2/5 1-3 小時 新手友好度 78/100
openvibely/openvibely#1443 ·
維護者通常 2 天內回覆
-
難度 2/5 1-3 小時 新手友好度 60/100
canonical/service-mesh#845 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 62/100
-
難度 2/5 1-3 小時 新手友好度 80/100
keyxmakerx/Chronicle#1179 ·
維護者通常 1 天內回覆