$ the-wire · showcase
PyRIT fixes objective inference and adds set_value verdicts; promptfoo prunes Azure and Git dependencies
By RepoJournal · Filed · About AI Red Teaming · Composed from the cited sources · methodology
PyRIT's scorer stack gets two changes that touch how verdicts and objectives are computed, while promptfoo's day was almost entirely dependency-pruning refactors with no operator-visible behavior change.
FIX: Infer the objective from the user request when tool calls precede the answer microsoft/PyRIT
Any scorer that inferred its objective from a target's request got an empty string whenever the target ran a tool loop, because the extraction only read the turn at sequence - 1 and found the function_call_output there. Both the sync and async extractors now reuse the lookup rule from MemoryInterface.get_request_from_response, so multi-turn tool-calling targets report an objective instead of bl...
FEAT Set true/false verdicts through Score.set_value (phase 14) microsoft/PyRIT
Score.set_value(value) now writes a true/false verdict and its status in one call, storing "true"/"false" and setting status alongside it, so a verdict can no longer drift out of step with its own status. Writing verdicts through score_value still works until 2.0, and float scores behave exactly as before, so nothing breaks on upgrade.
FIX: Remove TextTarget from GUI (#3777) microsoft/PyRIT
TextTarget is gone from the GUI, so orchestrators that relied on the text target in the web interface no longer have that entry point.
MAINT Prefer public package imports and enforce export boundaries microsoft/PyRIT
Imports in PyRIT now have to come through the public package paths, with export boundaries enforced. Custom scorer or orchestrator code that reached into internal modules may need its imports adjusted.
refactor(azure): replace the Foundry project SDK promptfoo/promptfoo
The promptfoo day was four dependency-swap refactors: Azure Foundry now uses the REST transport and existing OpenAI client, PFX signing calls the system OpenSSL with OPENSSL_BIN, Sheets reuses the existing Google auth library, and Code Scan uses native Git. Foundry, Sheets, Code Scan and signing behavior are documented as matching what they replaced; the only number that moved is the isolated r...