Consider providing a template for record feedback
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- documentation
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.
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.
- Dominant language
- Python
- Stars
- 49
- Forks
- 14
- Avg merge
- 4h 44m
- Merged PRs (30d)
- 15
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from psf/advisory-database
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
psf/advisory-database#162 · 5 comments ·
Maintainers usually reply within 1 day
-
Maintain all fixed versions on CVE record after upstream git branches are deletedMay be free again @sethmlarson claimed this 190 days ago, and no pull request is open. Open
psf/advisory-database#121 · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
psf/advisory-database#77 · 1 reaction ·
Maintainers usually reply within 1 day
All issues in psf/advisory-database
Similar issues
-
plot_graph crashes when a mesh node has no m2m edgePossibly taken @tygvi claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
mllam/neural-lam#883 · 1 comment ·
Maintainers usually reply within 2 days
-
enhancement possible-duplicate
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
AOSSIE-Org/PictoPy#1715 · 2 comments ·
Maintainers usually reply within 6 days
-
SQLite connector omits generated columns from the catalog, and drops relationships sourced on themOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
NVIDIA/auto-ontology#511 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ethereum/execution-specs#3996 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
cpp-best-practices/project_validator#267 ·
Maintainers usually reply within 1 day