Conversation
G-Rath
previously approved these changes
Aug 12, 2026
G-Rath
left a comment
G-Rath
left a comment
Collaborator
There was a problem hiding this comment.
ooohhh I just realized I'll need to figure out how WordPress versions work for semantic 🫠
…ted-level contract Refactor VersionStrategy from a per-version interface with numeric priorities to a slice-ordered, Affected-level contract using ExtractionState to atomically track consumed version entries and prevent duplicate extractions. Also unify CPE fallback extraction across cpeApplicability and affected[].cpes, memoize per-repo version tag resolution in ProcessRanges, and fix Linux conversion outcome counting in AddAffected.
jess-lowe
marked this pull request as ready for review
October 1, 2026 01:30
another-rex
reviewed
Oct 2, 2026
another-rex
left a comment
another-rex
left a comment
Contributor
There was a problem hiding this comment.
The PR description mentions extracting GIT, but I don't think the strategies actually extract git commits?
another-rex
reviewed
Oct 2, 2026
| wpPluginTracRegex = regexp.MustCompile(`plugins\.trac\.wordpress\.org/browser/([^/]+)`) | ||
| wpPluginSvnRegex = regexp.MustCompile(`plugins\.svn\.wordpress\.org/([^/]+)`) | ||
| wpPluginOrgRegex = regexp.MustCompile(`wordpress\.org/plugins/([^/]+)`) | ||
| wpThemeTracRegex = regexp.MustCompile(`themes\.trac\.wordpress\.org/browser/([^/]+)`) |
Contributor
There was a problem hiding this comment.
Can you change [^/] to also include /?# characters? Incase the url doesn't end on a trailing slash.
Contributor
Author
it did once upon a time. (one of those 37 commits ago lol) I'll look into it |
This branch has not been deployed
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
3 participants
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.
Adds support for extracting and converting WordPress vulnerability data (Core, Plugins, Themes) from CVE5 records, with tailored handling for Wordfence, Patchstack, and WPScan CNAs.
Changes
Rationale
WordPress records often rely on SVN or custom CNA identifiers rather than standard Git commits. This change enables high-fidelity ingestion of WordPress-specific data while retaining linkage to Git history where possible, ensuring comprehensive coverage for WordPress users.