Skip to content

deps: bump nltk to 3.10.3 - #196

Open
katsugtgz wants to merge 1 commit into
EvolvingLMMs-Lab:mainfrom
katsugtgz:deps/nltk-3.10.3
Open

deps: bump nltk to 3.10.3#196
katsugtgz wants to merge 1 commit into
EvolvingLMMs-Lab:mainfrom
katsugtgz:deps/nltk-3.10.3

Conversation

@katsugtgz

Copy link
Copy Markdown

Updates nltk to address the advisories listed below.

Evidence:

  • requirements.txt pinned nltk@3.9.1
  • osv-scanner reported PYSEC-2026-96, PYSEC-2026-97, PYSEC-2026-98, PYSEC-2026-99, PYSEC-2026-2078, PYSEC-2026-2085, PYSEC-2026-2235, PYSEC-2026-2236, PYSEC-2026-2237, PYSEC-2026-3581, PYSEC-2026-3582, PYSEC-2026-3583, PYSEC-2026-3584, PYSEC-2026-3657 and their linked GHSAs for nltk@3.9.1
  • updated version: 3.10.3

Validation:

  • osv-scanner --lockfile=requirements.txt no longer reports any advisory for nltk after the update
  • pip install nltk==3.10.3 and import nltk pass in a clean venv
  • the repo documents no runnable unit test command for this requirements file, so no test suite was executed

Note: osv-scanner still reports separate advisories for other packages in requirements.txt (datasets, protobuf, sentencepiece, and others). This patch only clears the nltk advisories.

Scope: dependency/lockfile update only.

requirements.txt pinned nltk 3.9.1. osv-scanner reported
PYSEC-2026-96/97/98/99, PYSEC-2026-3581..3584, PYSEC-2026-2078/2235/2236/2237,
PYSEC-2026-3657, PYSEC-2026-2085 and linked GHSAs for that pin.
osv-scanner reports no advisories for nltk 3.10.3.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant