# Grype: check an SBOM for vulnerabilities Check an SBOM for vulnerabilities. ## 1. Run the example [Download the Grype example](https://www.security.run/docs/examples/grype.zip). Extract it, install `httpx`, set your API URL and token, then run `python client.py`. The client uploads the included inputs, submits the command, and saves the result under `results/RUN_ID`. ## 2. Check the result Read report.json for vulnerability matches from the bundled database. Read the native exit code and cleanup status printed by the client. [Read results and save reports](https://www.security.run/docs/visibility.html) explains the returned files. ## 3. Use your own inputs Edit `example.json` to change the command arguments, requested outputs or deadline. Replace the files under `inputs/` with your own data, keeping the staged paths aligned with the command. The client creates the artifact IDs for you; illustrative IDs shown here must not be copied into a live request. ### Files used by this example - `sbom.json` The example uses supplied files or the disposable execution environment. Nothing from the environment carries into a later run unless you request and reuse its output. Qualified version: `0.121.3`. Commands: `grype`. - Uses an immutable bundled vulnerability database snapshot; no database download occurs during runs. Inspect `GET /v1/tools/grype` for the current installed version and readiness. The published snapshot has 1 functional case(s), plus timeout and cancellation checks. These examples demonstrate the native path; other flags and inputs are supported within the tool’s runtime limits. ## Command submitted by the example ```json { "tool": "grype", "timeout_seconds": 90, "invocation": { "args": [ "sbom:sbom.json", "-o", "json", "--file", "report.json" ], "outputs": [ "report.json" ], "success_exit_codes": [ 0 ], "executable": "grype", "files": [ { "path": "sbom.json", "artifact_id": "artifact_aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa", "executable": false } ] } } ```