Repository navigation
Add scoped search and CVE enrichment filters - #133
Merged
Merged
Conversation
jdaigneau5
approved these changes
Aug 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds scope-aware search across base CVE data, CNA containers, and ADP containers, then exposes structured SSVC, KEV, reference URL, and disputed-tag filters through
POST /search.The response contract remains unchanged:
scopecontrols where filters match, while successful searches continue returning complete CVE records.Changes
FULL,CNA_ONLY, andADP_ONLYscope enum.FULLis the default. Existing keyword, CWE, CVSS, rejection-state, identifier, date, and CPE filters now resolve fields according to the selected scope. CNA-only CPE applicability filters return HTTP 400 withADP_ONLY.utils/searchScope.js,utils/constants.js,controllers/middleware.js,routes/index.js,utils/searchQueryBuilder.jsssvcExploitation,ssvcAutomatable,ssvcTechnicalImpact,ssvcRole,ssvcTimestampStartDate, andssvcTimestampEndDate. Multiple SSVC conditions must match the same structured metric entry, with case-insensitive enums/role and inclusive timestamps.utils/ssvc.js,utils/searchContainerMetrics.js,utils/searchPostFilters.js,utils/searchQueryBuilder.js,controllers/searchController.jsknownExploitedboolean filtering plus inclusivekevDateAddedStartDateandkevDateAddedEndDateboundaries. Date-only stored values are interpreted as midnight UTC, and date filters requireknownExploited: true.utils/kev.js,utils/searchPostFilters.js,utils/searchQueryBuilder.js,controllers/middleware.js,routes/index.jsreferenceURLmatching across scope-selected container references. Matching is a case-insensitive literal substring; user wildcard metacharacters are escaped before query construction.utils/searchScope.js,utils/searchQueryBuilder.js,controllers/middleware.js,routes/index.jsdisputedboolean.truerequires the exact tag in at least one selected container;falseexcludes records with that tag in any selected container. No general-purpose record-tag filter is introduced.utils/searchScope.js,utils/searchQueryBuilder.js,controllers/middleware.js,routes/index.jsroutes/swagger.js,api-docs/openapi.json,README.mdutils/*.test.js,controllers/*.test.js,routes/*.test.js,api-docs/openapi.test.js,server.test.js