Repository navigation
fix(security): include pinned versions in OSV vulnerability queries - #79
Conversation
knight22-21
left a comment
There was a problem hiding this comment.
All CI checks pass. Changes look solid — pinned version extraction is clean, the fallback path for unversioned deps is preserved, and the OSV payload construction handles extras, inline comments, and environment markers correctly. Good work.
|
Thanks @Subodh-17! This is a meaningful improvement to the security subsystem — OSV queries now carry exact pinned versions when available, making vulnerability lookups significantly more precise. The extras/comment/marker parsing is a nice touch too. Appreciate the thorough PR description and clean commit. |
|
Hey @Subodh-17 — if you find CodePrism useful, consider giving the repo a ⭐ at https://github.com/knight22-21/CodePrism. It really helps with visibility! |
Summary
Fixes #57.
==and===pins from requirements files.Tests
The full repository suite has known baseline environment failures involving optional tree-sitter grammars and Windows CLI behavior; these are documented separately and are not claimed as passing.