Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Parent: LLM Vulnerability Scanner Feature Parity with Garak, Giskard, CyberSecEval

未关闭
#511 2 条评论 2 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 2 天内回复

@abdelhadi703 已经在做这个了。

开始于 2026年10月6日。

  • #1102 来自 @raghavendrakari —— 已关闭,未合并
  • #3009 来自 @abdelhadi703 —— 未关闭

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
冷清
技术栈
python
领域
security

调研方向

未确定实现文件、测试或入口点。首先比较 Garak、Giskard 和 CyberSecEval 支持的攻击场景与 PyRIT 已记录的功能,然后针对一个缺失的场景创建一个聚焦的后续 issue;当该场景具有明确的实现或文档范围时,即视为完成。

由索引模型根据 Issue 内容生成。

描述

good first issue help wanted

TLDR; We want help creating issues where Garak, Giskard, or CyberSecEval support an attack scenario where PyRIT doesn't support it.

Background

Other tools like Garak, Giskard, and CyberSecEval have different use cases from PyRIT, but there is overlap as well. If there is an attack in one of these other platforms, we probably want to support it also and would love issues being created so we can track this (or clarify if it already exists/improve our docs).

This paper tackles a really difficult problem, and that's comparing these tools (and PyRIT). When I was looking, some of the things I noticed that it mentioned PyRIT was lacking were:

  • Lack of multi-language support (I think we actually have this as a converter)
  • Lack of GCG (we have this as an auxiliary module)
  • Dan, AutoDan, etc (I think we have support for all of this. We certainly have DAN and ways to modify those prompts with GPTFuzz - but we would love to know what we're missing)
  • Insecure Coding Test (we don't have this, but it would be an easy scorer to write!)

And there might be more that I missed!

So as an example of issues we'd like, all of the above are good to open. Even if we think we support them (like in the multi-language case) we can dive into specifics to make sure we're not missing anything, and potentially improve documentation so it's more obvious these scenarios are supported.

Describe the solution you'd like

Please open follow-up sub-issues with any features you notice or find in these other tools that PyRIT doesn't have! That way we can track them. Also, we would love community to tackle any of these also, but it still can be helpful to open an issue so we can help guide :D

主要语言
Python
星标
4.6k
派生
924
平均合并
2 天 14 小时
30 天内合并 PR
227

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

  • 没有 Dockerfile 或 Docker Compose 文件
  • 有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

microsoft/PyRIT 的其他 Issue

查看 microsoft/PyRIT 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。