[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f29azqtywalkg3":3},{"code":4,"message":5,"data":6,"timestamp":26},10000,"success",{"full_name":7,"position":8,"description":9,"language":10,"stars":11,"forks":12,"stars_gained":13,"age_days":14,"hn_threads":15,"one_liner":16,"summary_md":17,"topic":18,"github_topics":21,"license":22,"homepage":23,"updated_at":24,"history":25},"bluechips-zhao\u002FDITING",23,"谛听 DITING：LLM 驱动的自主渗透测试工作台，Go + Next.js + PostgreSQL，基于 ARTEX（AGPL-3.0）","Go",119,12,8,14,[],"A self-hosted LLM workbench for authorized pentest tasks, with multi-agent runs, human approval and evidence-bound findings.","Adopt this only if you already run authorized engagements and can supply your own PostgreSQL, login password and model credentials; it is a working surface, not a turnkey scanner.\n\n## The problem\nA tester starting a scoped engagement has to keep the target inventory, recorded traffic, model conversations, candidate findings and the final report in separate tools, then reconcile them by hand. That makes it easy to lose which request produced a given finding or which report version was shared. DITING puts assets, scope rules, agent runs, captured traffic and findings into one self-hosted workspace, so a finding can be traced back to the request\u002Fresponse pair and regenerated into a report. The result is a single audit trail of the task rather than a folder of exports.\n\n## What's different\nThe project is a modified fork of ARTEX that keeps the asset graph, multi-agent exploration, traffic evidence and manual approval, and adds token\u002Ftool budgets, evidence relationships, report versions, full export and encrypted backup\u002Frestore [project instructions](https:\u002F\u002Fgithub.com\u002Fbluechips-zhao\u002FDITING\u002Fblob\u002Fmain\u002FREADME.md). The 2.6 release focuses on run observability: model-call usage accounting, execution statistics, and source\u002Freview status for candidate signals, which stay pending review rather than becoming confirmed vulnerabilities automatically [release notes](https:\u002F\u002Fgithub.com\u002Fbluechips-zhao\u002FDITING\u002Freleases\u002Ftag\u002Fv2.6.0). A budget mechanism with conservative reservation and a wind-down phase limits runaway loops, though the README states the token budget is a local usage ledger, not a vendor billing figure.\n\nThe trade-off is that the tool assumes operator judgement. Constraints only feed agent context while tool interception rules execute separately, so scope enforcement depends on configuring both. Candidate findings are deliberately not promoted automatically, which means human review is part of the workflow rather than optional polish.\n\n## Who should try it\nThis suits a penetration tester or small red team that wants a self-hosted LLM-assisted workspace over an authorized scope and is willing to supply a database and model configuration. Docker users get a compose template with separate persistent volumes for runtime secrets and workspace data, keeping keys out of the browsable data directory [backup notes](https:\u002F\u002Fgithub.com\u002Fbluechips-zhao\u002FDITING\u002Fblob\u002Fmain\u002Fdocs\u002FDOCKER_BACKUP.md). Those who want a one-click cloud scanner, or who cannot run PostgreSQL 16+ locally, should look elsewhere. Non-Windows users must build from source; the release ships a Windows amd64 package, and the Docker template is a source-build entry point rather than a prebuilt image.\n\n## Requirements and limitations\nFirst start is a blank business state: no demo database, admin password, model key or tasks are included, so setup means creating a PostgreSQL 16+ database, setting an 8-character-plus login password and configuring a model [getting started](https:\u002F\u002Fgithub.com\u002Fbluechips-zhao\u002FDITING\u002Fblob\u002Fmain\u002FREADME.md#开始使用). Source builds need Go 1.26.3+, Node 22, npm and PostgreSQL. The setup wizard binds to loopback and checks local origin, Host and a one-time launch token.\n\nOngoing care is the bigger cost. Model credentials and other secrets are encrypted with a separate `secrets.key`; losing or replacing it can halt startup, and backups need that key packaged or explicitly declared separately backed up. Upgrading from 2.3.x to 2.4.0 encrypts old credentials, so rolling back requires restoring a pre-upgrade database and workspace backup. The README also states the 2.6.0 container image was not rebuilt or accepted because Docker was unavailable at release; earlier 2.5 local records do not count as this release's image acceptance.\n\n## HotRepo's take\nHotRepo recorded 119 total stars and a #23 position on its NEW-REPOSITORY board (新项目榜, not the overall Trending board) on 2026-10-25, from a repository created 2026-10-11. There is no comparable daily-board history, so whether interest persists cannot yet be judged. Before investing time, verify the Windows release and the documented encrypted-backup restore path match your environment, since the recovery workflow is the part most likely to matter after real usage.",{"slug":19,"name":20},"security","Security & Privacy",[],"AGPL-3.0",null,"2026-10-25T06:48:02Z",[],1792919657]