osv: skip ECOSYSTEM ranges for Go and npm#1908
Merged
Merged
Conversation
The GitHub Advisory Database published advisories for the npm package nocodb using ECOSYSTEM range type instead of SEMVER (e.g., GHSA-4w6r-5c2j-qf5f). This happens because nocodb switched to calendar-based versioning (2026.04.1), which is not valid SemVer 2.0 — the advisory database chose ECOSYSTEM accordingly. The parser currently returns a hard error for ECOSYSTEM ranges on Go and npm ecosystems, added as a defensive check in a607a05 and 87be024. This error propagates through Parse, aborting the entire ecosystem update. This change skips the range with a warning instead, using the same pattern as GIT ranges. The advisory is recorded via stats.Ignored. Signed-off-by: J. Victor Martins <jvdm@sdf.org>
jvdm
force-pushed
the
jvdm/osv-skip-ecosystem-go-npm
branch
from
bc0c6fa to
78ab95f
Compare
9 tasks
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
2 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.
The GitHub Advisory Database published advisories for the npm package
nocodbusingECOSYSTEMrange type instead ofSEMVER(e.g., GHSA-4w6r-5c2j-qf5f). This happens because nocodb switched to calendar-based versioning (2026.04.1), which is not valid SemVer 2.0 — the advisory database choseECOSYSTEMaccordingly.The parser currently returns a hard error for
ECOSYSTEMranges on Go and npm ecosystems, added as a defensive check in a607a05 and 87be024. This error propagates through Parse, aborting the entire ecosystem update.This change skips the range with a warning instead, using the same pattern as
GITranges. The advisory is recorded viastats.Ignored.