Tags: google/osv.dev
Tags
fix: remove `index-url` from poetry requirements.txt (#4481) We don't want this to talk to artifact registry (I'm not 100% sure if this will work as-is)
test: update apitester snapshots (#4457) The snapshots have changed, probably due to OSV advisories being changed. Please review the differences to make sure that they're expected!
test: update vulnerability IDs in integration test (#4357)
chore: use `storage.googlepis.com/[bucket]` URLs everywhere (#4321) instead of `[bucket].storage.googleapis.com`, per https://docs.cloud.google.com/storage/docs/access-public-data#api-link
fix: limit number of search indices added to Bugs (#4285) [openSUSE-SU-2024:12948-1](https://osv.dev/vulnerability/openSUSE-SU-2024:12948-1) has so many upstream vulns that it made >6500 search_indices, which (combined with the other fields) was too many indexed properties for datastore to handle. Put a limit on the number of search indices populated from alias/upstreams to avoid this problem.
docs(blog): fix broken external link (#4133) This replaces the yuzu link in [Introducing broad C/C++ vulnerability management support](https://osv.dev/blog/posts/introducing-broad-c-c++-support/) with an archived version, since the original repository is no longer available. The example steps have also been updated to reflect the current flow verified locally. This should fix a `404` reported by the markdown-link-check action. There's still `429`/`403` issues but those can be fixed in a separate PR. --------- Co-authored-by: Rex P <[email protected]> Co-authored-by: Xueqin Cui <[email protected]>
fix(frontend): prevent pURL overflow in vulnerability details (#4105) Fixes a UI issue on the vulnerability details page, where extremely long pURLs would overflow outside their containers. This was spotted on [SUSE-SU-2025](https://osv.dev/vulnerability/SUSE-SU-2025:03333-1#:~:text=pkg%3Arpm/suse/avahi%26distro%3DSUSE%2520Linux%2520Enterprise%2520Module%2520for%2520Desktop%2520Applications%252015%2520SP6). The overflow also caused the layout to break completely on mobile displays, which should now be resolved.
PreviousNext