security: remediate dependency vulnerabilities #3
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.certifiRemediated findings
certifi2026.6.17GHSA-6q48-6c7w-9gw2Remaining 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.