cd /news/ai-agents/show-hn-pantry-an-open-source-scanne… · home › topics › ai-agents › article
[ARTICLE · art-173684] src=waffuru.ai ↗ pub= topic=ai-agents verified=true sentiment=↑ positive

Show HN: Pantry an open source scanner that checks what your coding agents run

Waffuru AI released Pantry 0.4.0, a free, MIT-licensed open source scanner for macOS, Linux and Windows that checks installed packages and repositories against open vulnerability and malware data and applies the fixes it can safely apply. Pantry runs locally, sends only package names and versions off the machine, and caches results so later scans take seconds; the tool is built to catch agent-specific attack paths that carry no CVE, including the 22 GitHub repos Bitdefender Labs found using AGENTS.md, CLAUDE.md, Claude Code session-start hooks, MCP configs and VS Code tasks to run hidden setup scripts that steal tokens, SSH keys and cloud credentials. Pantry also flags third-party scripts loaded without an integrity hash and code shaped like the Optimizely loader that hit 178 organisations' sites, and every release is signed, hashed and built reproducibly, verified via packslip, GitHub or cosign before installation.

key takeaway

Pantry 0.4.0 scans repos for code that runs on open — Claude Code and Gemini hooks, in-repo MCP servers and VS Code folder-open tasks — plus eval-decoded payloads and third-party scripts lacking integrity hashes, and names the version that fixes each finding.

read15 min views3 publishedNov 21, 2026
Show HN: Pantry an open source scanner that checks what your coding agents run
Image: source

Free · Open source · macOS, Linux and Windows

Before agents run on your machines, the machines have to be safe. Pantry checks everything installed on your Mac or Linux machine, and every repo on it, against open vulnerability and malware data. It reports only what actually applies, names the version that fixes it, and applies the fixes it safely can.

View the source on GitHub

Runs on

  • macOS

  • Windows

  • Linux

  • Ubuntu

  • Debian

  • Fedora

  • Arch

  • Omarchy

On Windows, Pantry checks your repos and a first few installed programs; full machine checks are coming. Tell us what you need

  • Free
  • Pantry costs nothing, and its MIT-licensed source code is open to everyone.
  • Local
  • Scans run on your machine. Only package names and versions ever leave it.
  • Fast
  • Later scans take seconds, because Pantry checks only what changed, from a cache on your disk.

Attacks don’t wait for a CVE. #

Agents now read your repos, run your tools and hold your keys. Two attacks from November 2026 show what that puts at stake. Neither came with a CVE, so a CVE feed would not have been helpful.

  • Bitdefender Labs · ### GitHub repos that hijack your AI coding agentBitdefender found 22 GitHub repos that get AI coding assistants to run a hidden setup script, through AGENTS.md and CLAUDE.md, a Claude Code session-start hook, MCP configs and VS Code tasks. The script steals tokens, SSH keys and cloud credentials, then plants the same configs in the victim’s other repos. What Pantry checks Code a repo runs the moment it is opened (Claude Code and Gemini hooks, MCP servers kept in the repo, VS Code tasks on folder open), payloads decoded at run time and fed to eval, and every MCP server your agents start. Read the report: GitHub repos that hijack your AI coding agent
  • Report URI · ### Malware on 178 organisations’ sites, through OptimizelyAn attacker added a to customers’ Optimizely Web project code. Pages at 178 organisations, some of the world’s largest brands among them, then swapped crypto addresses, skimmed cards, stole cookies and sent iPhones to exploit kits. What Pantry checks The payload lived in a vendor’s dashboard, out of reach of any scanner on your machine. Pantry flags the opening it used, third-party scripts your repos load without an integrity hash, and code shaped like the payload: strings decoded and fed to eval, clipboard address swaps and card data in the clear. Read the report: Malware on 178 organisations’ sites, through Optimizely

Install. Scan. Cache. Fix. #

One small binary does the whole job on your machine. Only package names and versions ever leave it.

Pantry can read your whole home directory, so every release is signed, hashed and built reproducibly. packslip, GitHub or cosign checks the download before it ever runs.

$ mise use -g packslip:github.com/waffuruai/pantry# verifies the signed packslip, then the binary’s digest$ wpantry versionwpantry 0.4.0 (rust, schema 1)
  1. Signed release
  2. Signature + SHA-256
  3. Your machine

A download that fails either check is never installed.

Example output from one machine. Yours will differ.

Secure your system. #

Choose how much you want to check yourself. Every route verifies the release before anything runs.

Recommended

With the install script

Picks the build for your machine, checks it against SHA256SUMS, verifies its signature with packslip, the GitHub CLI or cosign, and installs it to ~/.local/bin.

$ curl -fsSL https://waffuru.ai/pantry/install.sh | sh

Easy updates

With mise

mise is a more versatile and secure package manager than Homebrew. Install it and turn it on in your shell, then install Pantry. mise reads the release’s signed packslip and verifies it against our release workflow before installing anything, then remembers the signer for every update.

  1. Install mise and turn it on (zsh, the macOS default) #

$ curl -fsSL https://mise.run/zsh | sh$ source ~/.zshrc
  1. Or on bash (most Linux) #

$ curl -fsSL https://mise.run/bash | sh$ source ~/.bashrc
  1. Then install Pantry #

$ mise use -g packslip:github.com/waffuruai/pantry

By hand

Verify it yourself

Download the binary, check it against SHA256SUMS and at least one signature (its signed packslip, its GitHub build attestation or its cosign bundle), then install it.

$ ASSET=wpantry-universal-apple-darwin  # Linux: wpantry-x86_64-unknown-linux-musl or wpantry-aarch64-unknown-linux-musl$ BASE=https://github.com/waffuruai/pantry/releases/latest/download$ curl -fsSLO "$BASE/$ASSET" -O "$BASE/SHA256SUMS" -O "$BASE/packslip.sigstore.json"$ grep " $ASSET\$" SHA256SUMS | shasum -a 256 -c -$ packslip verify packslip.sigstore.json --artifact "$ASSET"  # or: gh attestation verify "$ASSET" --repo waffuruai/pantry$ install -m 0755 "$ASSET" ~/.local/bin/wpantry

Coming soon

Other package managers

Homebrew, apt, dnf, pacman and apk packages are on the way. Until then, install with the script or mise above.

$ brew install wpantry        # Homebrew, macOS and Linux$ sudo apt install wpantry    # Debian and Ubuntu$ sudo dnf install wpantry    # Fedora and RHEL$ sudo pacman -S wpantry      # Arch Linux$ sudo apk add wpantry        # Alpine

Then scan, see the plan, and write an HTML report.

$ wpantry scan$ wpantry fix --dry-run$ wpantry report --html

Reports in every format. #

Read it in your terminal, share one offline HTML page, or hand JSON to your tools and agents. wpantry report turns the latest scan into any of them, without scanning again.

One offline page to read, share or print: what was checked, what applies, the exact fix for each, and a prompt to hand your coding agent.

Example reports from one example project. Yours will differ.

See the whole report

Tables in your terminal, grouped by area, in the order to fix them, with the update plan at the end.

==> Security scan #1  2026-11-17 04:44 UTC · ~/.cache/wpantry/wpantry.db
  checked 3 project dependencies

Project dependencies  8 fail
    COMPONENT  VERSION  ADVISORY           SEVERITY  CVSS  EPSS   FIX
  ✗ smallvec   1.6.0    CVE-2021-25900     CRITICAL  9.8   1.7%   cd ~/code/app && cargo update -p smallvec --precise 1…
    ~/code/app/Cargo.lock · Buffer overflow in SmallVec::insert_many
  ✗ lodash     4.17.20  CVE-2021-23337 +3  HIGH      8.1   20.2%  cd ~/code/app && npm install lodash@4.18.0
    ~/code/app/package-lock.json · Command Injection in lodash
  ✗ requests   2.31.0   CVE-2024-47081 +2  MEDIUM    5.6   1.0%   Update requests to 2.33.0 in ~/code/app/requirements.…
    ~/code/app/requirements.txt · Requests vulnerable to .netrc credentials leak via malicious URLs

Update plan  wpantry fix runs the automatic ones
  needs you  cd ~/code/app && cargo update -p smallvec --precise 1.6.1  clears 1 finding
  needs you  cd ~/code/app && npm install lodash@4.18.0  clears 4 findings
  needs you  Update requests to 2.33.0 in ~/code/app/requirements.txt  clears 3 findings

✗ 3 thing(s) to update (8 advisories), 0 warning(s). See the plan: wpantry fix --dry-run

Example reports from one example project. Yours will differ.

Every finding with its severity, CVSS, EPSS and fix command, in a versioned schema for tools and agents.

{
  "schema": 1,
  "impl": "rust",
  "version": "0.4.0",
  "checked": { "project dependencies": 3 },
  "findings": [
    {
      "kind": "project",
      "component": "smallvec",
      "version": "1.6.0",
      "location": "~/code/app/Cargo.lock",
      "vuln_id": "CVE-2021-25900",
      "status": "fail",
      "fixed": "1.6.1",
      "kev": false,
      "severity": "CRITICAL",
      "cvss": 9.8,
      "cvss_version": "3.1",
      "epss": 0.0172,
      "epss_percentile": 0.77857,
      "note": "Buffer overflow in SmallVec::insert_many",
      "fix_cmd": "cd ~/code/app && cargo update -p smallvec --precise 1.6.1",
      "fix_auto": false,
      "dep_scope": "unknown",
      "dep_direct": true,
      "affected_range": ">=1.0.0, <1.6.1"
    },
    …
  ]
}

Example reports from one example project. Yours will differ.

One finding per line, joined with its OSV record, lifecycle and fix, for log pipelines.

{"affected_range":">=4.0.0, <4.17.21","aliases":["GHSA-29mw-wpgm-hmr9"],"component":"lodash","cvss":5.3,"cvss_version":"3.1","days_exposed":0.0,"dep_direct":true,"dep_scope":"runtime","epss":0.07424,"epss_percentile":0.94542,"first_seen":"2026-11-17 04:44 UTC","fix":null,"fix_auto":false,"fix_cmd":"cd ~/code/app && npm install lodash@4.17.21","fixed":"4.17.21","kev":false,"kind":"project","last_seen":"2026-11-17 04:44 UTC","location":"~/code/app/package-lock.json","note":"Regular Expression Denial of Service (ReDoS) in lodash","record":{"affected":[{"database_specific":{"source":"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2022/01/GHSA-29mw-wpgm-hmr9/GHSA-29mw-wpgm-hmr9.json"},"package":{"ecosystem":"npm","name":"lodash","purl":"pkg:npm/lodash"},"ranges":[{"events":[{"introduced":"4.0.0"},{"fixed":"4.17.21"}],"type":"SEMVER"}]},{"database_specific":{"source":"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2022/01/GHSA-29mw-wpgm-hmr9/GHSA-29mw-wpgm-hmr9.json"},"package":{"ecosystem":"npm","name":"lodash-es","purl":"pkg:npm/lodash-es"},"ranges":[{"events":[{"introduced":"4.0.0"},{"fixed":"4.17.21"}],"type":"SEMVER"}]},{"database_specific":{"source":"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2022/01/GHSA-29mw-wpgm-hmr9/GHSA-29mw-wpgm-hmr9.json"},"package":{"ecosystem":"npm","name":"lodash.trimend","purl":"pkg:npm/lodash.trimend"},"ranges":[{"events":[{"introduced":"4.0.0"},{"last_affected":"4.5.1"}],"type":"SEMVER"}]},{"database_specific":{"source":"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2022/01/GHSA-29mw-wpgm-hmr9/GHSA-29mw-wpgm-hmr9.json"},"package":{"ecosystem":"npm","name":"lodash.trim","purl":"pkg:npm/lodash.trim"},"ranges":[{"events":[{"introduced":"4.0.0"},{"last_affected":"4.5.1"}],"type":"SEMVER"}]},{"database_specific":{"source":"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2022/01/GHSA-29mw-wpgm-hmr9/GHSA-29mw-wpgm-hmr9.json"},"package":{"ecosystem":"RubyGems","name":"lodash-rails","purl":"pkg:gem/lodash-rails"},"ranges":[{"events":[{"introduced":"4.0.0"},{"fixed":"4.17.21"}],"type":"ECOSYSTEM"}],"versions":["4.0.0","4.11.2","4.12.0","4.13.1","4.14.1","4.15.0","4.16.1","4.16.3","4.16.4","4.16.6","4.17.10","4.17.11","4.17.14","4.17.15","4.17.2","4.17.4","4.17.5","4.3.0","4.5.1","4.6.1"]}],"aliases":["CVE-2020-28500"],"database_specific":{"cwe_ids":["CWE-1333","CWE-400"],"github_reviewed":true,"github_reviewed_at":"2021-03-19T22:45:28Z","nvd_published_at":"2021-02-15T11:15:00Z","severity":"MODERATE"},"details":"All versions of package lodash prior to 4.17.21 are vulnerable to Regular Expression Denial of Service (ReDoS) via the `toNumber`, `trim` and `trimEnd` functions. \n\nSteps to reproduce (provided by reporter Liyuan Chen):\n``` js\nvar lo = require('lodash');\n\nfunction build_blank(n) {\n    var ret = \"1\"\n    for (var i = 0; i < n; i++) {\n        ret += \" \"\n    }\n    return ret + \"1\";\n}\nvar s = build_blank(50000) var time0 = Date.now();\nlo.trim(s) \nvar time_cost0 = Date.now() - time0;\nconsole.log(\"time_cost0: \" + time_cost0);\nvar time1 = Date.now();\nlo.toNumber(s) var time_cost1 = Date.now() - time1;\nconsole.log(\"time_cost1: \" + time_cost1);\nvar time2 = Date.now();\nlo.trimEnd(s);\nvar time_cost2 = Date.now() - time2;\nconsole.log(\"time_cost2: \" + time_cost2);\n```","id":"GHSA-29mw-wpgm-hmr9","modified":"2025-09-29T21:12:31.102523Z","published":"2022-01-06T20:30:46Z","references":[{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2020-28500"},{"type":"WEB","url":"https://github.com/github/advisory-database/pull/6139"},{"type":"WEB","url":"https://github.com/lodash/lodash/pull/5065"},{"type":"WEB","url":"https://github.com/lodash/lodash/pull/5065/commits/02906b8191d3c100c193fe6f7b27d1c40f200bb7"},{"type":"WEB","url":"https://github.com/lodash/lodash/commit/c4847ebe7d14540bb28a8b932a9ce1b9ecbfee1a"},{"type":"WEB","url":"https://www.oracle.com/security-alerts/cpuoct2021.html"},{"type":"WEB","url":"https://www.oracle.com/security-alerts/cpujul2022.html"},{"type":"WEB","url":"https://www.oracle.com/security-alerts/cpujan2022.html"},{"type":"WEB","url":"https://www.oracle.com//security-alerts/cpujul2021.html"},{"type":"WEB","url":"https://snyk.io/vuln/SNYK-JS-LODASH-1018905"},{"type":"WEB","url":"https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1074893"},{"type":"WEB","url":"https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWERGITHUBLODASH-1074895"},{"type":"WEB","url":"https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWER-1074892"},{"type":"WEB","url":"https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARS-1074894"},{"type":"WEB","url":"https://snyk.io/vuln/SNYK-JAVA-ORGFUJIONWEBJARS-1074896"},{"type":"WEB","url":"https://security.netapp.com/advisory/ntap-20210312-0006"},{"type":"WEB","url":"https://github.com/rubysec/ruby-advisory-db/blob/master/gems/lodash-rails/CVE-2020-28500.yml"},{"type":"WEB","url":"https://github.com/lodash/lodash/blob/npm/trimEnd.js%23L8"},{"type":"PACKAGE","url":"https://github.com/lodash/lodash"},{"type":"WEB","url":"https://cert-portal.siemens.com/productcert/pdf/ssa-637483.pdf"}],"schema_version":"1.9.0","severity":[{"score":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","type":"CVSS_V3"}],"summary":"Regular Expression Denial of Service (ReDoS) in lodash"},"resolved_at":null,"schema":1,"severity":"MEDIUM","status":"fail","url":"https://osv.dev/vulnerability/GHSA-29mw-wpgm-hmr9","version":"4.17.20","vuln_id":"CVE-2020-28500"}
{"affected_range":"<4.17.21","aliases":["GHSA-35jh-r3h4-6jhm"],"component":"lodash","cvss":7.2,"cvss_version":"3.1","days_exposed":0.0,"dep_direct":true,"dep_scope":"runtime","epss":0.20158,"epss_percentile":0.97502,"first_seen":"2026-11-17 04:44 UTC","fix":null,"fix_auto":false,"fix_cmd":"cd ~/code/app && npm install lodash@4.17.21","fixed":"4.17.21","kev":false,"kind":"project","last_seen":"2026-11-17 04:44 UTC","location":"~/code/app/package-lock.json","note":"Command Injection in lodash","record":{"affected":[{"database_specific":{"source":"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2021/05/GHSA-35jh-r3h4-6jhm/GHSA-35jh-r3h4-6jhm.json"},"package":{"ecosystem":"npm","name":"lodash","purl":"pkg:npm/lodash"},"ranges":[{"events":[{"introduced":"0"},{"fixed":"4.17.21"}],"type":"SEMVER"}]},{"database_specific":{"source":"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2021/05/GHSA-35jh-r3h4-6jhm/GHSA-35jh-r3h4-6jhm.json"},"package":{"ecosystem":"npm","name":"lodash-es","purl":"pkg:npm/lodash-es"},"ranges":[{"events":[{"introduced":"0"},{"fixed":"4.17.21"}],"type":"SEMVER"}]},{"database_specific":{"source":"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2021/05/GHSA-35jh-r3h4-6jhm/GHSA-35jh-r3h4-6jhm.json"},"package":{"ecosystem":"npm","name":"lodash.template","purl":"pkg:npm/lodash.template"},"ranges":[{"events":[{"introduced":"0"},{"last_affected":"4.5.0"}],"type":"SEMVER"}]},{"database_specific":{"source":"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2021/05/GHSA-35jh-r3h4-6jhm/GHSA-35jh-r3h4-6jhm.json"},"package":{"ecosystem":"npm","name":"lodash-template","purl":"pkg:npm/lodash-template"},"ranges":[{"events":[{"introduced":"0"},{"last_affected":"1.0.0"}],"type":"SEMVER"}]},{"database_specific":{"source":"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2021/05/GHSA-35jh-r3h4-6jhm/GHSA-35jh-r3h4-6jhm.json"},"package":{"ecosystem":"RubyGems","name":"lodash-rails","purl":"pkg:gem/lodash-rails"},"ranges":[{"events":[{"introduced":"0"},{"fixed":"4.17.21"}],"type":"ECOSYSTEM"}],"versions":["0.10.0","0.7.0","0.8.1","0.8.2","0.9.0","0.9.1","0.9.2","1.0.0.rc.1","1.0.0.rc.2","1.0.0.rc.3","1.0.1","1.1.0","1.1.1","1.2.0","1.2.1","1.3.1","2.0.0","2.1.0","2.2.0","2.2.1","2.3.0","2.4.0","2.4.1","3.1.0","3.10.0","3.10.1","3.2.0","3.3.0","3.3.1","3.3.1.1","3.4.0","3.5.0","3.6.0","3.7.0","3.9.3","4.0.0","4.11.2","4.12.0","4.13.1","4.14.1","4.15.0","4.16.1","4.16.3","4.16.4","4.16.6","4.17.10","4.17.11","4.17.14","4.17.15","4.17.2","4.17.4","4.17.5","4.3.0","4.5.1","4.6.1"]}],"aliases":["CVE-2021-23337"],"database_specific":{"cwe_ids":["CWE-77","CWE-94"],"github_reviewed":true,"github_reviewed_at":"2021-03-31T23:59:26Z","nvd_published_at":"2021-02-15T13:15:00Z","severity":"HIGH"},"details":"`lodash` versions prior to 4.17.21 are vulnerable to Command Injection via the template function.","id":"GHSA-35jh-r3h4-6jhm","modified":"2026-10-17T02:55:38.085813876Z","published":"2021-05-06T16:05:51Z","references":[{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2021-23337"},{"type":"WEB","url":"https://github.com/lodash/lodash/commit/3469357cff396a26c363f8c1b5a91dde28ba4b1c"},{"type":"WEB","url":"https://www.oracle.com/security-alerts/cpuoct2021.html"},{"type":"WEB","url":"https://www.oracle.com/security-alerts/cpujul2022.html"},{"type":"WEB","url":"https://www.oracle.com/security-alerts/cpujan2022.html"},{"type":"WEB","url":"https://www.oracle.com//security-alerts/cpujul2021.html"},{"type":"WEB","url":"https://snyk.io/vuln/SNYK-JS-LODASH-1040724"},{"type":"WEB","url":"https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1074929"},{"type":"WEB","url":"https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWERGITHUBLODASH-1074931"},{"type":"WEB","url":"https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWER-1074928"},{"type":"WEB","url":"https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARS-1074930"},{"type":"WEB","url":"https://snyk.io/vuln/SNYK-JAVA-ORGFUJIONWEBJARS-1074932"},{"type":"WEB","url":"https://security.netapp.com/advisory/ntap-20210312-0006"},{"type":"WEB","url":"https://github.com/rubysec/ruby-advisory-db/blob/master/gems/lodash-rails/CVE-2021-23337.yml"},{"type":"WEB","url":"https://github.com/lodash/lodash/blob/ddfd9b11a0126db2302cb70ec9973b66baec0975/lodash.js#L14851"},{"type":"PACKAGE","url":"https://github.com/lodash/lodash"},{"type":"WEB","url":"https://cert-portal.siemens.com/productcert/pdf/ssa-637483.pdf"}],"schema_version":"1.9.0","severity":[{"score":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","type":"CVSS_V3"}],"summary":"Command Injection in lodash"},"resolved_at":null,"schema":1,"severity":"HIGH","status":"fail","url":"https://osv.dev/vulnerability/GHSA-35jh-r3h4-6jhm","version":"4.17.20","vuln_id":"CVE-2021-23337"}

Example reports from one example project. Yours will differ.

One row per advisory, for a spreadsheet or your security tooling.

id,aliases,url,component,kind,affected_version,safe_version,severity,kev,status,location,cvss,cvss_version,epss,epss_percentile
CVE-2020-28500,CVE-2020-28500,https://osv.dev/vulnerability/GHSA-29mw-wpgm-hmr9,lodash,project,4.17.20,4.17.21,MEDIUM,0,fail,~/code/app/package-lock.json,5.3,3.1,0.07424,0.94542
CVE-2021-23337,CVE-2021-23337,https://osv.dev/vulnerability/GHSA-35jh-r3h4-6jhm,lodash,project,4.17.20,4.17.21,HIGH,0,fail,~/code/app/package-lock.json,7.2,3.1,0.20158,0.97502
CVE-2021-25900,CVE-2021-25900 RUSTSEC-2021-0003,https://osv.dev/vulnerability/GHSA-43w2-9j62-hq99,smallvec,project,1.6.0,1.6.1,CRITICAL,0,fail,~/code/app/Cargo.lock,9.8,3.1,0.0172,0.77857
CVE-2024-35195,CVE-2024-35195 PYSEC-2026-1873,https://osv.dev/vulnerability/GHSA-9wx4-h78v-vm56,requests,project,2.31.0,2.32.0,MEDIUM,0,fail,~/code/app/requirements.txt,5.6,3.1,0.0034,0.27879

Example reports from one example project. Yours will differ.

Tables for a ticket, a pull request or a wiki page.


Scan #1 finished 2026-11-17 04:44 UTC on laptop.local by dev, wpantry 0.4.0; scope repos:~/code/app.

Checked 3 project dependencies.

## Project dependencies (8 fail, 0 warn)

| | Component | Version | Advisory | Severity | CVSS | EPSS | Why | Fix |
|---|---|---|---|---|---|---|---|---|
| ✗ | smallvec (~/code/app/Cargo.lock) | 1.6.0 | CVE-2021-25900 | CRITICAL | 9.8 | 1.7% | Buffer overflow in SmallVec::insert_many | `cd ~/code/app && cargo update -p smallvec --precise 1.6.1` |
| ✗ | lodash (~/code/app/package-lock.json) | 4.17.20 | CVE-2021-23337 +3 | HIGH | 8.1 | 20.2% | Command Injection in lodash | `cd ~/code/app && npm install lodash@4.18.0` |
| ✗ | requests (~/code/app/requirements.txt) | 2.31.0 | CVE-2024-47081 +2 | MEDIUM | 5.6 | 1.0% | Requests vulnerable to .netrc credentials leak via malicious URLs | `Update requests to 2.33.0 in ~/code/app/requirements.txt` |

Example reports from one example project. Yours will differ.

Verify everything on your computer. #

A pantry check covers what you have, what is past its date, what needs to be replaced and what someone has tampered with.

  • Everything installedRuntimes and compilers (every version your version managers keep), package managers, CLI tools, datastores, Docker, Homebrew, mise and global packages.

  • Every repo’s lockfileCargo, npm, pnpm, yarn, bun, Deno, Swift, Go, uv, poetry, pip, Bundler, Composer, Maven, Gradle, NuGet and more, before vulnerable code ships.

  • OS, browsers and appsmacOS Software Update, the major Linux distributions’ packages, Chrome, Firefox, Electron apps and other apps against their latest releases.

  • End of lifeRuntimes and datastores that no longer get security fixes, with the date they stopped.

  • Malware, not just CVEsEvery package name against the OpenSSF malicious-packages index, and look-alike names one keystroke away from a popular package.

  • Leaked secretsCredentials committed anywhere in a repo’s git history, reported redacted, plus weak passwords written into code and card numbers left in the clear.

  • Your AI coding toolsWhat Claude Code, Codex, Cursor, Gemini CLI and other agents actually run: their MCP servers, plugins, skills and bundled packages, and any server that always runs the latest release.

  • Repos that run on openA cloned repo can run code the moment your agent or editor opens it. Pantry finds those hooks, tasks and install scripts, and the marks of known hijacked-repo campaigns. Check a clone before you open it.

  • Hidden instructionsText that reads one way and runs another: Trojan Source, invisible characters that smuggle instructions to your AI assistant, prompts hidden in READMEs and pages, and links built to leak what an agent read.

  • Suspicious codePayloads decoded at run time, credential stores read and sent, keyloggers, code asking your crypto wallet to sign its account away, and sudo or persistence where they do not belong.

  • Booby-trapped documentsPDFs that run JavaScript, Office files with macros or remote templates and images hiding a program, in your repos and in Downloads, Desktop and Documents. ClamAV too, when it is installed.

  • Crypto clippersMalware that swaps a wallet address you copied for its own. Pantry tests the clipboard, finds the startup items and extensions that do it, and can guard the clipboard while you work.

  • Editor extensionsExtensions against VS Code’s malicious list, and whether your editors wait before installing a new version, so a hijacked release is pulled before it reaches you.

  • Your machine’s settingsDisk encryption, the firewall, Gatekeeper and SIP, automatic updates, sharing services, the screen lock and whether your DNS leaves the machine encrypted.

  • Compromised certificate authoritiesYour system, OpenSSL, Homebrew, Python and Node trust stores, checked against certificate authorities known to be distrusted. Pantry can distrust them for you until your OS update ships.

  • Supply-chain riskLicenses outside your allowlist, install scripts, prebuilt binaries with no source, and the container images your repos build from.

  • Exposed, with no fix yetFor a critical or actively exploited bug with no patch, Pantry says what to do meanwhile, can check hourly for the fix, and installs a stopgap where it has one, such as for a Linux kernel TCP flaw.

  • Breached accountsOnly if you say yes: whether your email address appears in a known data breach.

Open data sources we check. #

Open data only, no paywall. Every finding carries its advisory ID, so you can check it at the source.

Built to be trusted. #

A security tool sees your whole machine. So Pantry keeps its own footprint small and every claim checkable.

  • No telemetryPantry never reports on you. The only thing it sends is package names and versions, to OSV.dev, to look them up.

  • No AIPlain, deterministic code. The same machine gets the same answer, every time.

  • Written in RustMemory-safe, with unsafe code forbidden, compiled to one static binary.

  • Dependency-lightA handful of pinned Rust crates, each one vetted. No runtime to install.

  • Versioned and hashedEvery release is tagged, rebuilt byte for byte before it ships, and listed in SHA256SUMS.

  • Verified releasesCheck a download against its signed packslip, its GitHub build attestation or its cosign signature, before it runs.

  • Reads firstA scan changes nothing. Fixes run only when you ask, and nothing runs with sudo without asking first.

  • Reduced false positivesPantry reports only what applies to the exact versions on your machine. If a source cannot be reached, it says “not checked”, never safe.

  • Free and open sourceMIT licensed. Read every line, fork it, and run it on as many machines as you like.

For you, your agents and your fleet. #

The same binary on a laptop, inside your coding agent, in CI or across a few hundred servers.

  • PeopleRun it, read the plan, apply the safe fixes. The exit code says whether anything still needs you. People

$ wpantry fix --dry-run
  • AgentsStructured JSON and a bundled skill (wpantry skill) teach your coding agent to triage and fix, without ever running sudo. Agents

$ wpantry scan --json --no-input
  • Fleets and CIPoint it at a checkout, skip the machine, and fail the build when something has a released fix. Fleets and CI

$ wpantry scan --path . --no-machine --json

Questions, answered #

What leaves my machine? #

Package names and versions, sent to OSV.dev, plus downloads of public data such as CISA’s Known Exploited Vulnerabilities list and endoflife.date. File contents, paths and secrets never leave. The optional email breach check is the one exception, and it runs only after you say yes.

Does it need sudo? #

No. Pantry runs as you. Fixes that need sudo, like operating system packages, are printed for you to run yourself. A few optional stopgaps, such as distrusting a leaked certificate authority, ask for sudo before they change anything.

Why is it free? #

Because security should not depend on what you can pay. Vulnerability data behind a paywall leaves the people who can least afford a breach the most exposed. Pantry uses open data, and it is free for everyone.

How is this different from a CVE feed? #

A feed lists everything that broke, anywhere. Pantry tells you what applies to the exact versions on your machine, and which version fixes it.

Why is it called Pantry? #

A pantry check tells you what you have, what is past its date and what has been recalled. That is the job. The command is wpantry.

Does it run on Windows? #

Yes, from Pantry 0.5.0. On Windows, Pantry checks your repos (lockfiles and dependencies), searches advisories and writes reports. It reads the installed programs from the registry and checks a first few, such as VMware Workstation and ASUS Armoury Crate, against CVE records; more are added as they are reviewed. Package managers (winget, Scoop, Chocolatey), Windows Update and the certificate store are coming. Install it with mise, or with the install script from Git Bash.

Can my AI agent use it? #

Yes. wpantry scan --json gives your agent structured findings, and wpantry skill prints a skill that teaches it to triage and fix, and never to run the steps that need sudo.

Check your pantry. #

Free, open source and verified before it runs. Read the source first if you like. That is the point.

── more in #ai-agents 4 stories · sorted by recency
── more on @waffuru ai 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
→ Live at https://your-agent.zahid.host ✓
Get free account → Pricing
from €0/mo · no card required
LIVE [news/show-hn-pantry-an-op…] indexed:0 read:15min 2026-11-21 · —