snyk / snyk/snyk-python-plugin
Support for PEP751 pylock.toml file
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 23
- Forks
- 30
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 3
Description
Will Snyk be adding support for the new PEP751 pylock.toml lock file format? ( https://peps.python.org/pep-0751/ )
I have a repository using a uv workspace with no root Python project and am interested in adding Snyk to it. The comments in https://github.com/snyk/snyk-python-plugin/issues/251 and https://github.com/astral-sh/uv/issues/11181 provide a workaround (generating a requirements.txt file that Snyk can parse), but that workaround is not very feasible for large monorepo projects. I know uv supports the pylock.toml file format and am wondering if Snyk is planning to support it as well (since that's a tool-agnostic standard, maybe it's easier to support?).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading PEP 751 and the workaround discussions in snyk-python-plugin#251 and astral-sh/uv#11181. No source files or tests are named; done means the plugin supports scanning a uv workspace's pylock.toml file without requiring a generated requirements.txt.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100