security: remediate dependency vulnerabilities #1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "security/grype-dependency-fixes"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Automated dependency security remediation
This pull request was generated by the scheduled Forgejo dependency-security workflow.
Syft created a Python dependency SBOM from the repository (including
poetry.lock), Grype scanned that SBOM, and Poetry was asked to re-resolve only packages for which Grype reported an available fix.The workflow does not widen dependency constraints in
pyproject.toml. If a safe version cannot be selected inside the existing constraints, the workflow leaves that decision for a maintainer instead of changing policy automatically.idna,pygments,requests,urllib3Remediated findings
idna3.11GHSA-65pc-fj4g-8rjxpygments2.19.2GHSA-5239-wwwm-4pmqrequests2.32.5GHSA-gc5v-m9x4-r6x2urllib32.6.3GHSA-mf9v-mfxr-j63jurllib32.6.3GHSA-qccp-gfcp-xxvcRemaining findings after the lockfile update
None.
Validation
The workflow re-ran Syft and Grype against the updated lockfile and ran
poetry check --lockbefore pushing this branch.2962b4ff19d0c6b103c2