Check your project dependencies
Upload the dependency file of a Python (Django, FastAPI, Flask) or Node.js application. A few seconds later you see which packages have known security vulnerabilities and which version to update to.
Supported files: requirements.txt (including pip freeze output), poetry.lock, uv.lock, pdm.lock, Pipfile.lock, package-lock.json, yarn.lock, pnpm-lock.yaml. No account, no charge. Continuous monitoring of several projects with e-mail alerts: from $25 a month.
Sample result
The result for the three packages in the box above (Django 4.2.7, Django REST framework 3.14.0, gunicorn 20.1.0), database as of 21 November 2026. Shown here: the three most serious vulnerabilities per package; the actual result lists all of them.
Packages
3
Vulnerable
3
Important issues
21
- important
django4.2.7 → update to5.2.1746 known vulnerabilities, 16 important.
- CVE-2026-15307 important Django GeoDjango spatial lookups allow file writes and outbound requests through GDAL raster parsing · fixed in 5.2.17
- CVE-2026-3902 important Django vulnerable to ASGI header spoofing via underscore/hyphen conflation · fixed in 4.2.30
- CVE-2026-33034 important Django: SGI requests with a missing or understated `Content-Length` header could bypass the `DATA_UPLOAD_MAX_MEMORY_SIZE` limit · fixed in 4.2.30
- important
djangorestframework3.14.0 → update to3.18.26 known vulnerabilities, 3 important.
- CVE-2026-114137 important Django REST framework: TokenProxy.delete() reports success and revokes nothing · fixed in 3.18.2
- CVE-2026-114136 important Django REST framework: JSONParser applies an attacker-named codec to the request stream · fixed in 3.18.2
- CVE-2026-114138 important Django REST framework: Accept header with many large quoted parameters burns ~19s of CPU per request in content negotiation · fixed in 3.18.2
- important
gunicorn20.1.0 → update to22.0.02 known vulnerabilities, 2 important.
- CVE-2024-6827 important Gunicorn HTTP Request/Response Smuggling vulnerability · fixed in 22.0.0
- CVE-2024-1135 important Request smuggling leading to endpoint restriction bypass in Gunicorn · fixed in 22.0.0
What you get
- A list of vulnerable packages, most serious first: name, the version in your project and the version that removes every known vulnerability.
- Every vulnerability with its CVE number and a link to the source, with severity and the fixed version.
- Packages that could not be checked – those without a pinned version – listed separately instead of silently skipped.
What happens to the file
The file is read in memory and is not stored. Only package names and versions are sent to the vulnerability database – the same information a public registry sees on every install. We do not need or look at your application code.
In a CI pipeline
The same check works from the command line and returns JSON:
curl -s -F file=@requirements.txt "https://webskan.com/api/deps/check?format=json"
The vulnerablePackages field is the number of packages with vulnerabilities; each one carries updateTo, the version to update to.
Continuous monitoring: an e-mail when a new vulnerability appears
Dependencies that are clean today may have a vulnerability announced next month – the code has not changed, the knowledge about it has. A one-off check shows today's state. Monitoring compares the package lists of your projects with the vulnerability database every day and writes only when there is something new.
One command in CI
After purchase you get a ready-to-use curl command. Your CI pipeline uploads the dependency file on every deploy, so the list is always current.
Daily check
Every morning we compare the packages of each project with the database of known vulnerabilities. Nothing to run, nothing to remember.
A specific e-mail
A new vulnerability affects a project? You get a message: which package, which vulnerability and which version to update to. We do not repeat the same vulnerability every day.
curl -s -F file=@requirements.txt \ "https://webskan.com/api/deps/push/YOUR_TOKEN?project=shop-backend"
3 projects
- Up to 3 projects, Python and Node.js
- Daily check of every project
- E-mail about a new vulnerability with the version to update to
- Cancel any time
10 projects
- Up to 10 projects, Python and Node.js
- Daily check of every project
- E-mail about a new vulnerability with the version to update to
- Cancel any time
Card payments are handled by Polar; the subscription renews monthly until cancelled. We store package names and versions only – we do not need or see the application code. You can remove a project and connect another one at any time.
Where the data comes from
From OSV.dev, which aggregates the GitHub Advisory Database (CC-BY 4.0), the PyPA Advisory Database (CC-BY 4.0) and the OpenSSF malicious packages list, among others. Webskan is not affiliated with these organisations. What is visible from outside your site is covered separately by the security score.