NVIDIA-NeMo / NVIDIA-NeMo/Guardrails
feature: re-enable PyPI trusted publishing with attestations
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.2k
- Forks
- 842
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 25
Description
Did you check the docs?
- I have read all the NeMo-Guardrails docs
Is your feature request related to a problem? Please describe.
The publish-pypi-approval.yml and publish-wheel.yml workflows are currently disabled and publishing is done manually with no Sigstore signatures; this can be considered a supply chain security risk
Downstream consumers that rebuild or redistribute nemoguardrails would benefit from a more verifiable upstream provence
Describe the solution you'd like
- Diagnose why the existing workflows failed and re-enable them to use PyPI trusted publishing with attestations
Describe alternatives you've considered
n / a
Additional context
See also Recommended attestation verification for PyPI packages
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 inspecting .github/workflows/publish-pypi-approval.yml and .github/workflows/publish-wheel.yml to determine why publishing was disabled. Review the workflow configuration and its recent failures, then verify that the workflows use PyPI trusted publishing and produce Sigstore attestations. Done means automated publishing works with verifiable attestations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- ci-cd, release, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100