Skip to content

Issues: aboutcode-org/vulnerablecode

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

576 Open 440 Closed
576 Open 440 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Improve display of the Severity table of the Essentials screen data-quality design-needed Priority: high ui
#1732 opened Jan 7, 2025 by mjherzog
severity vectors bug: Do not list ALL duplicated severity vectors in the UI. Also display the score bug ui
#1729 opened Jan 6, 2025 by pombredanne
fedcode-next: Collect additional data to support automated curation of vulnerability data
#1727 opened Jan 5, 2025 by pombredanne
4 tasks
fedcode-next: Create curation queue for VulnerableCode data enrichment
#1726 opened Jan 5, 2025 by pombredanne
5 tasks
fedcode-next: Prepare vulnerability data enrichment and curation automation
#1725 opened Jan 5, 2025 by pombredanne
2 tasks
fedcode-next: Code pipeline and models to continuously collect various URLs and references to articles, other advisories
#1724 opened Jan 5, 2025 by pombredanne
fedcode-next: Code pipeline and models to continuously collect scripts and vulnerability scanner rules to detect if the vulnerability is "expressed"
#1723 opened Jan 5, 2025 by pombredanne
fedcode-next: Code pipeline and models to continuously collect related PoC for exploits of a vulnerability
#1722 opened Jan 5, 2025 by pombredanne
fedcode-next: Code pipeline and models to continuously automatically collect fix commits
#1721 opened Jan 5, 2025 by pombredanne
fedcode-next: Code, UI and models to expose and curate extra mitigation possibilities
#1720 opened Jan 5, 2025 by pombredanne
fedcode-next: Code, UI and models to curate severity scoring
#1719 opened Jan 5, 2025 by pombredanne
fedcode-next: Code, UI and models to assign and qualify the weakness exposed by a CVE (or CWE)
#1718 opened Jan 5, 2025 by pombredanne
fedcode-next: Code, UI and models to curate PURL and VERS package version range for packages affected and fixing a vulnerability
#1717 opened Jan 5, 2025 by pombredanne
fedcode-next: Core UI and models to expose a sorted vulnerabilities curation queue
#1716 opened Jan 5, 2025 by pombredanne
fedcode-next: Code framework to automatically tag as "curated" the base data that only needs quick or no human review
#1715 opened Jan 5, 2025 by pombredanne
VCIO-next: The vulnerability details view UI is too slow to render bug
#1714 opened Jan 3, 2025 by tdruez
1
@TG1999
1
Collect all fix commits
#1703 opened Dec 20, 2024 by pombredanne
5 tasks
Improve getting started
#1702 opened Dec 19, 2024 by pombredanne
1
OSV importer not present
#1700 opened Dec 16, 2024 by Hritik14
@TG1999
VCIO-next: Create improver to detect issues difficulty:hard enhancement
#1699 opened Dec 13, 2024 by pombredanne v37.0.0 - 4-next
3
VCIO-next: Audit VCIO for own security
#1698 opened Dec 13, 2024 by pombredanne
2 tasks
v37.0.0 - 4-next
1
Collect existing fix commits and patches open datasets fix-commit
#1697 opened Dec 13, 2024 by pombredanne
10 tasks
VCIO-next: Create improver to find fix commits feature fix-commit improver
#1696 opened Dec 13, 2024 by pombredanne v36.0.0 - 3-next
@TG1999
VCIO-next: Improve tracking of fix commits
#1695 opened Dec 13, 2024 by pombredanne
2 tasks
Failing to import Github OSV
#1694 opened Dec 11, 2024 by TG1999
@ziadhany
ProTip! Type g i on any issue or pull request to go back to the issue listing page.