Cybersecurity toolkits · Rank #37
AutoRedTeam-Orchestrator
Grade C: derived only from the two verdicts below. How grades work
MCP-native security automation workbench (SDK + CLI + MCP) — authorized testing + static AI/MCP attack-surface self-audit to SARIF / GitHub Code Scanning
Why this verdict
How we check →- 54 commits in the last 90 days, none in the last 30. receipt ↗
- OpenAI SDK 1 declared; latest is 3 (2 majors behind). receipt ↗
- On current major: Pydantic. receipt ↗
- Not counted in verdict: Anthropic SDK 0 → 1. receipt ↗
Snapshot: commit 596dbca on main, checked 2026-10-19 07:18 UTC. Receipts link to files at this exact commit.
- No license detected: check terms before commercial use.
- Two or more breaking releases behind on a core dependency.
Dependency freshness
| Package | Declared | Latest | Status |
|---|---|---|---|
| OpenAI SDK openai | 1.12.0 | 3.35.1 | 2 majors behind |
| Anthropic SDK anthropic | 0.18.0 | 1.15.0 | Behind, not counted |
| Pydantic pydantic | 2.6.0 | 2.14.1 | Current |
Declared = lowest version the kit's dependency file (package.json, pyproject.toml or requirements.txt) allows. Latest = the npm "latest" tag or the newest PyPI release. TypeScript, the Stripe SDK, FastAPI and other 0.x packages are shown but not counted in the verdict.
What's in the stack
- API layer
- Pydantic
Detected from declared dependencies. A listed package means it's installed, not necessarily fully wired up.
What the README says you get
- AIAI/MCP static self-audit
对**你自己的仓库**做纯静态审计:盘点 MCP server 与 AI agent 工具的攻击面
- APIMCP Server access
MCP Server 把安全能力暴露为 MCP 工具,供 AI 编辑器或 Agent 调用
- APIPython SDK
SDK 是 `core/` 引擎之上的薄异步封装
- OtherTyper CLI
Typer CLI 是本地分析的主入口,也是安装后的 `autort` 命令
- OtherCapability manifest
manifest(`core/capability_manifest.py`)是每个暴露 MCP surface 的机器可读、单一事实来源
- OtherCVE intelligence search
`cve-search` | CVE 情报
- OtherNuclei scanning
`nuclei` | 纯 Python Nuclei 扫描
- OtherReport generation
`report` | 生成报告
- OtherPort scan and recon
`scan` | 端口扫描 / 完整侦察
- TestingCI severity threshold
`--ci` 输出精简摘要,并在发现达到 `--severity-threshold`(info/low/medium/high/critical)的项时返回非零退出码
Extracted from the kit's README by a local AI model (deepseek-flash) on Sep 29, 2026. Every item is checked against an exact README quote; 4 unverifiable items were discarded. A README claim is the maker's description, not something we tested.
Watch AutoRedTeam-Orchestrator
Get told if it goes dormant, gets archived, falls further behind on a core dependency, or changes its license or price.
History
Sep 29, 2026 → Oct 19, 2026. One square per check, colored by maintenance status. Hover for details.
Show as a table
| Date | Maintenance | Dependencies | Commits (90d) |
|---|---|---|---|
| Oct 19, 2026 | Steady | 2+ majors behind | 54 |
| Oct 12, 2026 | Active | 2+ majors behind | 54 |
| Sep 29, 2026 | Active | 2+ majors behind | 54 |
Sources
Every claim on this page comes from these public records, checked . Open them to verify.
- Commit history ↗ default branch (main) at the checked commit: pulse, contributors, last commit
- Releases ↗ latest release
- pyproject.toml ↗ declared dependency versions and stack (at commit 596dbca)
- requirements-core.txt ↗ declared dependency versions and stack (at commit 596dbca)
- requirements.txt ↗ declared dependency versions and stack (at commit 596dbca)
- README ↗ quoted features at the checked commit
- PyPI ↗ latest versions of Python packages (each linked in the table above)