chore(trivy): ignore base-image setuptools and pip-vendored msgpack findings - #252
Merged
Conversation
…indings Trivy started flagging setuptools 70.3.0 (CVE-2025-47273) and msgpack 1.1.2 (GHSA-6v7p-g79w-8964) in the python:3.12-slim base image's own tooling. Neither is in Sam's runtime tree under /home/sam/.local, and Sam never calls setuptools.PackageIndex or unpacks msgpack data. Every open PR fails ci-checks on these two rows since #243 merged; pushes to main skip ci-checks, so main looks green while no PR can pass.
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.
What is this change?
Two lines in
.trivyignore, with rationale in the file: setuptools 70.3.0 (CVE-2025-47273) and msgpack 1.1.2 (GHSA-6v7p-g79w-8964), both from thepython:3.12-slimbase image's own tooling.What led to this?
After #243 merged, PR #251's re-run still failed the trivy step on exactly these two Python rows. Neither package is in Sam's runtime tree (
/home/sam/.local, fromrequirements.txt) or inrequirements-dev.txt. Sam never callssetuptools.package_index.PackageIndexand never unpacks msgpack data. Pushes tomainskipci-checks, somainreads green while every open PR is blocked.Tier
Tier 1: CI configuration, no runtime change.
Re-evaluate
On the next base image bump: drop both lines once the image ships setuptools >= 78.1.1 and a pip vendoring msgpack >= 1.2.1.