{
  "id": 2873424,
  "title": "Microsoft archived PyRIT (Mar 2026) - what LLM red-teamers should use instead",
  "url": "https://urgent.news/2026/08/23/microsoft-archived-pyrit-mar-2026-what-llm-red-teamers-should-use",
  "topic": "ai",
  "section": "AI",
  "published": "2026-08-23T20:55:52.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/ventrova/microsoft-archived-pyrit-mar-2026-what-llm-red-teamers-should-use-instead-3oo1"
  },
  "original_language": "en",
  "account": "Microsoft archived PyRIT (Python Risk Identification Tool) on GitHub on March 27, 2026, making it read-only with no further updates. PyRIT was a framework for custom attack sequences, not a turnkey scanner. If you were using PyRIT for a broad, actively maintained app-layer scanner, you should use promptfoo, which offers 50+ red-team plugins, OWASP/NIST/MITRE ATLAS report mappings, and regular releases. If you needed model-layer testing, such as jailbreaks, encoding tricks, or data leakage on the base model, garak is a good option. Giskard offers OWASP-mapped detectors and a paid tier for continuous scanning. For a fast, zero-setup smoke test, sentinel-scan-cli, a dependency-free CLI in Python and npm, has 15 attack patterns mapped to OWASP LLM Top 10 categories. While none of these replace PyRIT's specific multi-turn orchestration, they offer alternatives for general LLM testing.",
  "summary": "Quick one: if PyRIT (Microsoft's Python Risk Identification Tool) is on your shortlist for LLM red-teaming, check the repo first. Azure/PyRIT was archived on GitHub on March 27, 2026. It's read-only now: no commits, no releases, no issue triage, nothing. Whatever version you pip-installed is the last version you'll ever get. That matters more for PyRIT than it would for most tools, because PyRIT…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}