Update the path-to-regexp package
A library that reads web addresses can be made to freeze your app with one crafted request. Updating it closes the hole.
In package-lock.json
Security for apps built with AI
Connect a GitHub, Bitbucket, or Origin project, or paste a git address. After every push, Suricode checks the code and tells you what to fix, in plain words. Your coding agent does the fixing.
Suricode
HomeProjectsYour agent
A
Home
Security score
Needs work
100 means nothing to fix. Every confirmed fix lowers it, leaked keys the most.
How is this calculated?
Things to fix
12
Confirmed by the AI review
Fix next
Fixed
0
issues fixed in the last 7 days
0 all time
This week
6
commits across your projects
8 scans finished
Fix next
Update a packageHigh6
Change some codeHigh1
Change a settingHigh5
Update a package
Bump axios in the web app
acme/shopweb/package-lock.json
Bump undici to a patched 6.x release
acme/apipackage-lock.json
Refresh browser plugin build dependencies
acme/shopbrowser/package-lock.json
Refresh the web build and test toolchain
acme/shopweb/package-lock.json
Update the affected tooling dependency chain, or add a lockfile override, so ‘braces’ resolves to a fixed version.
A package used by this project’s build and developer tools can be crashed by specially crafted pattern text.
acme/apipackage-lock.json
Upgrade sharp to a patched release
acme/apipackage-lock.json
In plain words
What a scanner says
CVE-2024-45296 path-to-regexp <8.0.0
CWE-1333 Inefficient Regular Expression Complexity
CVSS 7.5 HIGH package-lock.json:4120
What Suricode says
A library that reads web addresses can be made to freeze your app with one crafted request. Updating it closes the hole.
In package-lock.json
What it finds
None of them take a security degree to understand. Suricode finds them and explains each one in a sentence.
An API key or password sitting in the code. Whoever finds it can run up your bill or read your users’ data.
A library you installed has a known hole. If a fixed version exists, you update. If it does not, Suricode closes the hole anyway.
A form, a query, or a file upload written exactly the way attackers hope. Usually a few lines to fix.
Dockerfiles, CI workflows, and server configs that leave a door open.
How it works
Step 1
Sign in with your email. Pick a GitHub, Bitbucket, or Origin repository, or paste a git address. Suricode only ever gets read access.
Step 2
Every push starts a check. We also check on a schedule when nothing changed, because a library can pick up a new hole in code you never touched. Minutes later you get a short list: what to fix, why it matters, how urgent it is.
Works with your agent
Copy a single fix, or connect your agent. You paste one prompt into it, once. From then on it scans after every push and works through what Suricode found.
The prompt you paste once. The full one is waiting in the app, under Your agent.
1. Scan after every push.2. Wait for the result, then read the fixes.3. Fix the leaked keys first. Then the rest.4. Push, and scan again to confirm.
After a push, your agent queues a check. It waits instead of polling.
{ "job": { "status": "queued", "expectedFinishAt": "2026-10-08T14:06:00Z" }}
Then it reads a short list. Trimmed here to one fix.
{ "fixes": [ { "verdict": "fix", "title": "Update the path-to-regexp package", "plainSummary": "One crafted request can freeze your app.", "findings": [ { "filePath": "package-lock.json", "severity": "high" } ] } ]}
Patched packages
Most of your app runs on community packages, kept up by volunteers in their spare time. A fix can take weeks. Sometimes the maintainer moves on, and the patched version never comes. Suricode does not wait for it: we build a patched copy of the version you already run, and handle it for you.
Without Suricode
A scanner says update. There is no new version, and there may never be one. The hole stays open, or you jump a major release and hope nothing breaks.
With Suricode
You get a patched build of the version you already run. Same package, same API, hole closed. Your agent installs it like any other fix.
Your agent gets these steps with the fix. The key stays in an environment variable.
# .npmrc in the project root (no secret in it)@suricode:registry=https://pkg.suricode.ai/npm///pkg.suricode.ai/npm/:_authToken=${SURICODE_TOKEN} # package.json: same version, patched build"overrides": { "<package>": "npm:@suricode/<package>@<version>-suricode.1"}
For Python, the Suricode index sits next to PyPI.
pip install --extra-index-url "https://__token__:${SURICODE_TOKEN}@pkg.suricode.ai/pypi/simple/" # requirements.txt: same version, patched build<package>==<version>+suricode.1
You keep the package you already run. Its API does not change.
The hole is closed whether the maintainer is slow, busy, or gone for good.
No jumping a major version and hoping the rest of the app still builds.
Why not just ask your agent?
An agent asked to check security reads what it can afford to open. We read the whole project, so more holes show up. Your agent then spends its tokens on the fix, not on the hunt.
Your agent does not search the project. It gets a short list: what to fix, why it matters, and how. The tokens go to the change, not to reading the codebase.
Scanners go through the whole repository, including the lockfiles, Dockerfiles, and configs an agent tends to skip. A short AI review keeps the real ones.
Questions
Suricode builds a patched copy of the version you already run. You stay on that version, the hole is closed, and you do not wait for the maintainer or jump a major release.
No. Every finding says what it is, why it matters, and what to do, in everyday words. The technical details are one click away, for your agent.
No. Suricode only reads your code. Your coding agent makes the changes, in your editor, where you can see them. That includes installing a patched package we give you.
Suricode is free. Adding a project and getting a check costs nothing.
JavaScript and TypeScript, Python, Go, Ruby, PHP, Java, Kotlin, Swift, Rust, C# and C/C++, plus Dockerfiles, Kubernetes, Terraform, nginx, and GitHub Actions. Suricode works out your stack on every check and runs the tools that fit it.
Yes. Connect GitHub through our read-only GitHub App, Bitbucket through its sign-in, or Origin through the read-only Origin App. For anything else, paste a git address with an access token or an SSH key.
Each check fetches your project into a private working copy on our scanner. The tools and an AI reviewer read it there to decide which findings are real. Nobody else has access. What you see in Suricode is the list of findings and the plain explanations.
Every new push starts another one. For GitHub, Bitbucket, and Origin projects that happens on its own. For a project added by git address, press Scan again, or let your agent start it.
Sign in with your email. No password, nothing to install.