FEAT Proposal: Turkish Prompt-Injection dataset loader (design/provenance discussion)
@3nesdeniz ya está trabajando en esto.
Desde el 12/9/2026.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
Opening this as a design-first proposal before asking for a merge, following the catalog-direction guidance from @adrian-gavrila on #2175 (propose and get maintainer direction before building).
What
A SeedDatasetProvider loader for the open Turkish Prompt-Injection dataset (3nesdeniz/turkish-prompt-injection-1k, CC BY 4.0): paired benign/attack Turkish examples across instruction override & system-prompt extraction, jailbreak personas, obfuscation & data exfiltration, and agentic tool abuse, with Turkish morphological variation.
Why it could be valuable
- Multilingual coverage gap: PyRIT's injection-related seed datasets are English-first. Guardrails that pass in English often fail to generalize; Turkish (rich morphology) is a useful stress test for OWASP LLM01.
- False-positive measurement: the benign hard negatives share surface vocabulary with the attacks, so detector over-blocking is measurable, not just recall.
Provenance (being upfront)
This is not backed by a peer-reviewed paper today. What exists: an openly published, CC BY 4.0 dataset with a CITATION.cff, a pinned immutable HF revision, and a documented deterministic/reproducible generation methodology; split-isolated train/val/test with no template leakage.
Question for maintainers
Given that most loaders are paper-backed, what evidence-of-value / provenance bar would you want here before this is a candidate — e.g. a peer-reviewed or preprint write-up of the methodology, third-party usage, or something else? I'd rather align on direction first than repeat the sequencing issue from #2174/#2175.
A tested implementation is ready as a draft PR (#2365) purely for reference; I'm not requesting review of it until the direction here is settled.
- Lenguaje dominante
- Python
- Estrellas
- 4.5k
- Forks
- 896
- Merge medio
- 3 d 8 h
- PR fusionados (30 d)
- 191
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de microsoft/PyRIT
-
BUG HarmBench loader drops ContextString, so contextual behaviors are sent without their context Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
Todos los issues de microsoft/PyRIT
Issues similares
-
agent-ready documentation needs-triage
Dificultad 1/5 1-3 horas Aptitud para principiantes 88/100
-
documentation
Dificultad 1/5 Menos de una hora Aptitud para principiantes 91/100
-
workflow-status page template still says reusable workflows are "triggered only by workflow_call:" Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 92/100
-
Add https://search.jeremyh.xyz/ Abiertoinstance instance add
Dificultad 1/5 Menos de una hora Aptitud para principiantes 72/100
searxng/searx-instances#939 · 1 comentario ·
-
area-deployment area-integrations triage:bot-seen
Dificultad 2/5 Medio día Aptitud para principiantes 86/100