Support easy access to the json version of a vulnerability

[G-Rath]

Is your feature request related to a problem? Please describe.
"I'm always frustrated when ..." I keep having to lookup the API endpoint for getting the JSON of an osv 😅

Describe the solution you'd like
Having a link to the underlying JSON data that is used by the api, or something like supporting adding .json to the end of the URL to show the JSON version.

Describe alternatives you've considered
Writing the api path on a sticky note, but I'm concerned if I add too many more of those my monitor will fall off my desk due to the weight :/

[another-rex]

A current two click workaround is going to https://osv.dev/CVE-2023-45802 and then clicking the import source link, which should give you the JSON.

Though allowing .json to be appended directly to the URL is probably still a good idea.

[G-Rath]

I almost mentioned that but I didn't - the import source is useful but not quite the same since part of the APIs role is cleaning up/improving/whatevering the osv from the original source and sometimes that isn't even json (e.g. for https://osv.dev/vulnerability/PYSEC-2024-50 the source is YAML).

[oliverchang]

Can you file a feature request in the OSV.dev repo to support a .json URL suffix ? We can probably easily redirect to https://api.osv.dev/v1/vulns/ID

[G-Rath]

Is there an actual other repository you'd like an issue opened against, or was that just a case of Friday-afternoon-brain? 😅

[oliverchang]

Friday-afternoon-brain :) My bad!