Check dependencies
check_stackCheck exact package versions for known vulnerabilities. Pass a lockfile's contents (package-lock.json, bun.lock, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, uv.lock, Pipfile.lock, Cargo.lock, go.sum, Gemfile.lock, composer.lock, mix.lock, packages.lock.json, gradle.lockfile, .github/workflows/*.yml, action.yml, pubspec.lock, Package.resolved, renv.lock, Manifest.toml, cabal.project.freeze, *.opam.locked) with its filename, an SBOM (CycloneDX JSON, SPDX 2 JSON, Syft JSON, e.g. from syft <image> -o cyclonedx-json; up to 10 MB) in the same field, or a package list. An SBOM's language packages are checked like a lockfile's; its OS packages (deb, apk, rpm and Arch alpm purls) are matched against the distro advisories for their release and come back in "os" (findings with the fixed version per package; releases with no advisories on file are marked unchecked, never guessed, and Arch-based distros such as Manjaro as unchecked "derivative"; a finding or package with possible: true comes from Arch's tracker, which gives no introduced version, so the version may predate the bug: say "may be affected"; keep the license objects of share-alike distro data with it). A language finding with unreviewed: true was matched on the maintainers' own GitHub advisory, or on the packages a CVE record names when its CNA's scope covers them, which GitHub has not reviewed yet: say so. A finding with inferred: true was matched on a package inferred from the CVE's product name and repository (no advisory lists the package), by the CVE's own version range: say it probably applies; unchecked items with reason "inferred" are such packages whose CVE gives no versions to compare, and with reason "maintainer" packages a maintainers' advisory names with a range Intel can't compare for that version, and with reason "cve" packages a CVE record names whose versions don't decide that one: say they may be affected. A GitHub Actions workflow or action.yml works too: each uses: owner/repo@ref is checked, a floating tag (v4) as the newest release of its line; refs pinned to a commit SHA (without a "# v1.2.3" comment) or a branch come back in "unchecked" with the advisories on file. Also lists versions endoflife.date marks as out of support (eol). No matches means none were found, not that the packages are safe.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "check_stack"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| filename | No | Lockfile name, e.g. "package-lock.json". Detected from content if omitted (SBOMs always are). | |
| lockfile | No | Full text of the lockfile or SBOM. | |
| packages | No | Alternatively, packages at exact versions. |