DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to look up security advisories for a dependency with Oc

Query the OSV database for a GHSA, CVE, or ecosystem id and read a compact result.

  • Research
  • Intermediate
  • 15 minutes
  • From the README
  • Claude Code
  • Codex
  • Cursor

Authorization notice. Oc is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Who it is forA security-minded developer or agent reviewing a dependency alert before upgrading.

The problemAdvisory pages are long and mix in navigation, which wastes tokens when only the affected versions and fix matter.

The outcomeA compact view of the advisory record for a known id, ready to paste into a triage note.

What you need first

  • Node.js 20 or newer and npm
  • A terminal the agent or you can run commands in
  • Permission to install an npm package globally, or use npx instead

Steps

  1. Run npm install -g @only-cli/oc
  2. Run oc osv vuln <id> with a GHSA or CVE id from your alert (inferred, check the README)
  3. Run oc raw if you need the full record

Prompt for your agent

Use the only-cli/oc repo: run `oc osv vuln <advisory-id>` with the id from the dependency alert. Expect a compact advisory view with the affected package and versions. Verify the id in the output matches the alert before acting on it.

Caveat. The README does not show the exact output layout of the OSV shortcut, so confirm the fields you need with Oc raw on the first run.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page