Use Trusted Publishing to upload to PyPI
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.9k
- Forks
- 1.4k
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
which will provide PEP 740 attestations: https://trailofbits.github.io/are-we-pep740-yet/
and reduce the risk of supply chain attacks.
For details, see https://pydevtools.com/handbook/explanation/why-use-trusted-publishing-for-pypi/
Contributor guide
No contributing guide indexed for this repository
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
No files, tests, or entry points are named. Start by locating the repository's current PyPI upload and release workflow, then review how Trusted Publishing can provide PEP 740 attestations. Done means releases upload through Trusted Publishing and the resulting packages include the expected attestations while reducing supply-chain risk.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ci-cd, release, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100