Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

FEAT Add role-aware Scenario target-attempt accounting

Aperta
  • Qualcosa non va?
#3,043 3 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

@Nimit3418 ci sta già lavorando.

Dal 9/10/2026.

  • #3062 di @Nimit3418 — aperta

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
azure, python, sqlite
Ambito
backend, data, databases

Direzione di ricerca

Start with pyrit/analytics/scenario_statistics.py, pyrit/backend/services/scenario_progress_read_model.py, and pyrit/memory/memory_interface.py, plus the AttackResultMetadata contract and doc/code/framework.md. Trace how shared analytics policy reaches memory aggregation and backend/SDK/report consumers; the issue also calls for SQLite runtime and Azure SQL compilation parity checks. Done means adding role-aware target-facing counts while preserving existing logical-progress and raw-history semantics, with the listed edge cases covered.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

feature-request help wanted
Is your feature request related to a problem? Please describe.

Current main records producer roles but does not use them for target-attempt
rollups. The shared analytics helper, progress, and history SQL count attempts
without a producer-role predicate. Thus their existing
logical-unit/raw-history counts must not be presented as target-attempt counts.

For example, two target-facing child results plus one Sequential envelope
are three historical result rows, but only two target-facing producer attempts.
The envelope can still complete one outer planned logical unit. A preparation
error may also have a target-facing role, so this role alone does not prove a
target request occurred. This check inspected code; it did not run an attack.

Describe the solution you'd like

Add a consumed typed target-facing accounting projection using the existing
AttackResultMetadata contract and shared Scenario analytics/identity policy.
Keep planned logical progress, raw historical attempts, and target-facing
attempts distinct. Memory owns database aggregation; backend/SDK/report
consumers present the shared policy rather than independently infer roles.

Acceptance criteria:

  • Orchestration envelopes remain observable but contribute zero to target-facing
    attempts and their target-facing error/retry totals.
  • Preserve exact saved-plan denominators, outer-unit completion, existing
    latest-attempt identity/order, raw history, and #2551/#2820 cache inclusion.
    Add the new rollup without silently redefining existing unit/raw fields.
  • Legacy/malformed roles remain explicitly unknown using conservative decoding;
    never infer a role from a conversation ID, class name, display text, or index.
    Keep orchestration and unknown-role totals visible alongside target-facing
    totals so the producer categories reconcile with raw history.
  • Report unmatched attempts separately, with the same matching policy across
    progress, detail, SDK/report consumers, and history.
  • Real-domain/SQLite parity cases cover ordinary/baseline, flat and nested
    Sequential/Adaptive, retry/resume, recovered and unrecovered errors,
    preparation failure, negative retries, unknown roles, invalid plans,
    tied timestamps, and cache hits.
  • SQLite runtime and Azure SQL compilation cover equivalent database-side
    role filtering. Do not add full-result hydration, per-attempt queries, or
    Python grouping as a replacement for the new SQL aggregate.
  • Field names and documentation say target-facing producer attempts, not
    confirmed target invocations; no new request-tracing feature is required.

Dependencies: merged #2997 and #2820; coordinate indexed analytics #2792 and
history-query extractions #2768/#2769. The separate child-link fix #3039 and
dataset/technique UX are not hard dependencies for counting persisted roles.

Describe alternatives you've considered, if relevant

Do not redo shared success statistics, change logical completion to child
counts, or remove historical rows. Exclude schema/duplicate hierarchy stores,
child-link repair, hierarchy endpoints/UI, dataset/estimate changes, request
tracing, scorer semantics, and new attack algorithms.

Additional context

Roadmap: scope 8.
Design: original result/accounting references.
Evidence: upstream 58a93534838ed58e766276c060c4f0d9149d6483,
pyrit/analytics/scenario_statistics.py,
pyrit/backend/services/scenario_progress_read_model.py, and
pyrit/memory/memory_interface.py.
Follow doc/code/framework.md: models own types, analytics owns counting
policy, memory persists/aggregates, and backend/output present it.
No GUI change or unrelated screenshots are requested.

Lingua principale
Python
Stelle
4.6k
Fork
924
Merge medio
3g 4h
PR unite (30g)
264

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

  • Nessun Dockerfile né file Docker Compose
  • Ha un modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di microsoft/PyRIT

Tutte le issue di microsoft/PyRIT

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.