finnandClaude Opus 5.5
53081dd553
Only the direct dependencies were pinned. Werkzeug, Jinja2, MarkupSafe, itsdangerous and the other transitive packages were resolved at build time, so builds of the same commit could differ, and pip did not verify the downloaded files. There was also no vulnerability scan. - requirements.in / requirements-dev.in list the direct dependencies. requirements.txt / requirements-dev.txt are lockfiles generated by pip-compile with exact versions and hashes for every package. The dev lockfile is constrained by the production one. - Makefile targets: lock-deps, update-deps, sync-deps and audit (pip-audit against requirements.txt). - The locked production versions match the previously installed ones. The first audit found no known vulnerabilities. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
8 lines
137 B
Plaintext
8 lines
137 B
Plaintext
# Development tools. Generated into requirements-dev.txt by `make lock-deps`.
|
|
-c requirements.txt
|
|
black
|
|
flake8
|
|
isort
|
|
pip-audit
|
|
pip-tools
|