Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do not coerce ECOSYSTEM to SEMVER for ecosystems that do not strictly adhere to SEMVER #2916

Open
andrewpollock opened this issue Nov 26, 2024 · 3 comments
Labels
data quality Issues with data quality stale The issue or PR is stale and pending automated closure

Comments

@andrewpollock
Copy link
Contributor

Describe the bug
OSV.dev coerces to SEMVER records it imports for specific ecosystems, regardless of what version type the source has published, e.g. GitHub Advisory Database and the Go ecosystem

To Reproduce
Compare and contrast:

Expected behaviour
A record's type field is preserved as published

Screenshots
Compare and contrast:

Additional context
Credit to @Churro for surfacing this:

@andrewpollock andrewpollock added the data quality Issues with data quality label Nov 26, 2024
Copy link

✨ Thank you for your interest in OSV.dev's data quality! ✨

Please review our FAQ entry on how to most efficiently have this addressed.

@oliverchang
Copy link
Collaborator

Some more context here: ossf/osv-schema#314

Copy link

This issue has not had any activity for 60 days and will be automatically closed in two weeks

See https://github.com/google/osv.dev/blob/master/CONTRIBUTING.md for how to contribute a PR if you're interested in helping out.

@github-actions github-actions bot added the stale The issue or PR is stale and pending automated closure label Jan 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
data quality Issues with data quality stale The issue or PR is stale and pending automated closure
Projects
None yet
Development

No branches or pull requests

2 participants