Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 8 included reviews per hour; 7 remain after this review. Walkthrough新增 ChangesDark-Moon 安全扫描条目
Estimated code review effort: 1 (简单) | ~5 分钟 Merge Risk: ⚪ Minimal · up to This adds Dark-Moon to the security-scan catalog and propagates its English description into generated documentation. The metadata entry is ready to merge with no identified current-head risk. Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment Warning |
This adds Darkmoon under the 安全扫描 (security scan) category, following resources/CONTRIBUTING.md by placing a single items/安全扫描/dark-moon.yaml so the README table regenerates automatically.
Darkmoon (ASCIT31/Dark-Moon) is an open source (GPLv3) autonomous penetration testing platform. 50 specialist agents drive 50+ offensive tools over MCP across web, API, Active Directory, Kubernetes and cloud, and every finding carries proof of exploitation. It is self hosted, and a privacy gateway tokenizes sensitive target values before any cloud model sees them.
Why it fits this repo: the security scan section already lists third party offensive and code security tools such as trufflehog, gshark, veinmind-tools and sonarqube. Darkmoon serves the same ops audience that needs to scan and validate the security of their infrastructure, and it is a self hosted GitHub project so all yaml fields render correctly.
Disclosure: I contribute to Darkmoon. I am proposing this because it directly supports this repository's documented use case, and I am happy to adjust or withdraw it if maintainers consider it out of scope.
Summary by CodeRabbit