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

Potentially incorrect versions entries in PYSEC-2024-115 & PYSEC-2024-53

未关闭
#5,578 1 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 1 天内回复

@jess-lowe 已经在做这个了。

开始于 2026年7月7日。

评估

这个 Issue 还没有评估数据。

描述

It seems that https://api.osv.dev/v1/vulns/PYSEC-2024-115 and https://api.osv.dev/v1/vulns/PYSEC-2024-53 have PIP version constraints in their versions:

"langchain-openai==0.1.25",
"langchain-core==0.2.40",
"langchain-community==0.2.17",
"langchain-openai==0.1.24",
"langchain-groq==0.1.10",

Looking at the spec for versions I think this might technically be valid but afaik it's never been done before and it won't work with the offline logic in osv-scanner because it expects to be comparing versions only.

It looks like this is being added by osv.dev as the upstream (e.g. https://github.com/pypa/advisory-database/blob/main/vulns/langchain/PYSEC-2024-115.yaml) does not include these versions.

I picked this up via the semantic workflow in the osv-detector repo that runs the library from osv-scalibr across all the available versions in each ecosystem

主要语言
Go
星标
3k
派生
382
平均合并
1 天 10 小时
30 天内合并 PR
130

环境准备

从这里开始

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

google/osv.dev 的其他 Issue

查看 google/osv.dev 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

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