netbox-community/netbox dependency check

The premier source of truth powering network automation. Open source under Apache 2. Try NetBox Cloud free: https://netboxlabs.com/products/free-netbox-cloud/

netbox-community/netbox: 1 finding to fix, none critical.

Last checked against GitHub, OSV.dev, deps.dev, PyPI and endoflife.date.

1 thing your coding agent doesn’t know about this repo

netbox-community/netbox on GitHub (opens in a new tab)

1 warning9 low priority

One task with every fix, most urgent first, the file to change and why. Paste it into Claude Code, Cursor or Codex.

2 versions come from a range because no lockfile pinned them, so we checked the lowest version each range allows. Where that changes the advice, the finding says so.

Add this badge to your README

It shows today’s result and links to this report, so anyone opening the repo sees what needs fixing.

StackPrism dependency check badge for netbox-community/netbox
[![StackPrism](https://stackprism.ai/badge/github/netbox-community/netbox.svg)](https://stackprism.ai/check/github/netbox-community/netbox)

Ask Prism Agent about netbox-community/netbox

Map the repo (free) and ask what to fix first, whether an upgrade is safe, or what breaks if a service goes down. Prism Agent checks live sources before it answers.

How this report works

StackPrism read pyproject.toml and requirements.txt from the default branch of netbox-community/netbox and checked its 49 packages against GitHub, OSV.dev, deps.dev, PyPI and endoflife.date. Nothing was installed or run, and there’s no AI in the findings: each one comes from a source you can open.

Vulnerabilities come from OSV.dev, with known-exploited ones from CISA marked and listed first. Runtimes, frameworks and base images are checked against endoflife.date, and packages against their registry for deprecations and major versions you’ve fallen behind. The fix task above lists every change with the file to edit.

This page refreshes every few hours; after you push a fix, “Check again” runs it now. Only the repo’s root is read. For an app in a sub-folder, paste the folder’s link into the dependency check, and for a private repo, connect GitHub.