Advisories for packages
get_advisoriesCheck npm packages for security advisories. Start here before installing, upgrading or deploying: send 1 to 50 package names (never versions) and get, per package, its total and up to 20 advisories of the last 120 days, newest first, each with vulnerable ranges, fixed versions and the conditions that make it exploitable. A package with none returns total 0. Compare the ranges with your lockfile. For a daily check, pass since (the time of your last check) to get only what is new. For one advisory in full use get_advisory; for the version to upgrade to, use latest_safe.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"packages": "<packages>"
},
"name": "get_advisories"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| since | No | Only advisories new since this ISO date or date-time ("2026-10-27" is UTC midnight, or "2026-10-27T08:00:00Z"): published, or first read by Patchwire, after it. For a daily check, pass the time of your last check. Omit for the last 120 days. | |
| packages | Yes | npm package names as written in package.json, 1 to 50, for example ["next", "@supabase/supabase-js"]. Names only, never versions: compare the returned ranges with your lockfile. |