Skip to content

Fix CPE version range boundary validation - #140

Merged
jdaigneau5 merged 1 commit into
devfrom
af/version-range-fixes
Aug 31, 2026
Merged

jdaigneau5 merged 1 commit into
devfrom
af/version-range-fixes

Conversation

@afoote-mitre

@afoote-mitre afoote-mitre commented Aug 31, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

  • Reject negative numeric values and the standalone CPE NA value as ordered versionStart/versionEnd boundaries.
  • Preserve negative signs in semantic CPE version comparisons so values such as -1 and 1 cannot compare as equivalent.
  • Add unit, route-integration, OpenAPI contract, and generated Postman regression coverage.
  • Clarify the distinction between the 10,000-result pagination window and the 10,000-candidate semantic post-filter limit in README and Swagger documentation.

Version tokenization previously discarded a leading minus sign, causing a boundary such as -1 to compare as equal to 1 and return unintended matches. The API documentation also did not clearly distinguish direct-search exact totals from bounded semantic candidate totals.

@afoote-mitre afoote-mitre self-assigned this Aug 31, 2026
@jdaigneau5
jdaigneau5 merged commit 56c9894 into dev Aug 31, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants