fix(security): hash-lock the fuzz build, ignore the unfixed nltk advisory - #226
Merged
Merged
Conversation
.clusterfuzzlite/build.sh installed the two first-party packages with their dependencies unhashed (Scorecard #178). Their runtime deps now come from requirements/fuzz.txt with --require-hashes, compiled at 3.11 (the base-builder-python interpreter), and the packages go in with --no-deps. atheris and pyinstaller stay with the base image. integrations/llamaindex/osv-scanner.toml ignores GHSA-8mgp-746c-j5xp (Scorecard #34) until 2026-12-24. nltk reaches that directory through llama-index-core and 3.10.3, the latest release, is still affected. osv-scanner reads the file per directory, so a root copy would not apply. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two Scorecard follow-ups left after #225.
#178, PinnedDependencies,
.clusterfuzzlite/build.sh. The build installedagentrust-capture-coreandagentrust-trace-adaptersand let pip pull their dependencies unhashed. Those dependencies (agentrust-trace,cryptographyand 14 transitive packages) now come fromrequirements/fuzz.txtwith--require-hashes, compiled with uv at Python 3.11 because that is whatbase-builder-pythonships (3.11.13). The two packages then go in with--no-deps. atheris, pyinstaller and setuptools are installed by the base image'sinstall_python.sh, so they stay out of the lock.cflite_pr.ymlnow also triggers onrequirements/fuzz.txt.Verified: fresh 3.11 venv,
pip install --require-hashes -r requirements/fuzz.txt, both packages with--no-deps,pip checkclean, and every import the three fuzz targets make succeeds. osv-scanner 2.6.0 on the new lock: no issues.#34, Vulnerabilities, nltk GHSA-8mgp-746c-j5xp. nltk reaches
integrations/llamaindex/requirements-interop.txtthroughllama-index-core==0.14.24. OSV lists it aslast_affected: 3.10.3, and 3.10.3 is the newest release on PyPI, so there is nothing to bump to.integrations/llamaindex/osv-scanner.tomlignores that one ID until 2026-12-24 with the reason written in the file, and the README note gains a line pointing at it.The file sits next to the manifest, not at the repo root. osv-scanner applies a config only to manifests in its own directory, and a root copy left the finding in place when I ran it. With the file in
integrations/llamaindex/, osv-scanner 2.6.0 reports "GHSA-8mgp-746c-j5xp and 2 aliases have been filtered out". Scorecard's Vulnerabilities check calls osv-scanner'sDoScanwith no config override, and its docs say to putosv-scanner.tomlnext to the manifest, so it should clear on the next Scorecard run.Checks:
validate_integrations.py(41 integrations, 0 failures), the six validate pytest files (28 passed),validate_compatibility.py, both--checkgenerators, and ruff with the lint.yml selection, all clean.Generated with Claude Code