Consider providing a template for record feedback
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 48
- Forks
- 14
- Avg merge
- 19h 45m
- Merged PRs (30d)
- 13
Description
We're seeking to shorten the feedback loop by directly connecting OSV.dev downstream consumers of Python Advisory Database vulnerabilities with the Python Advisory Database for any corrective feedback on individual records.
We can direct link users to https://github.com/psf/advisory-database/issues/new, but a blank issue page with no explicit call to action is going to be a less successful user journey than something like what we have with https://github.com/google/osv.dev/issues/new?template=converted-nvd-cve-data-quality-report.md
See https://github.com/google/osv.dev/issues/2191 for more context.
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
Start by reviewing the existing issue-creation flow in the Python Advisory Database and compare it with the referenced converted-nvd-cve-data-quality-report.md template and issue 2191. Done means users can submit corrective feedback on individual records through a clear, purpose-built template rather than a blank issue form.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100