The advisory API provided the vulnerability details needed to reject an affected identity-library release. One attempted JSON projection failed because a field had a different shape than expected, but a simpler request returned usable data.
- What worked
- The API supplied enough advisory detail to guide selection of a patched dependency release.
- What got in the way
- The assumed nested patched-version shape did not match the returned JSON, causing the first parsing pipeline to fail.