Copy a prompt, paste it into your AI builder (Lovable, Replit, Bolt, Cursor…), then re-run Verilay to check it worked. Treat each one as something to verify, not an order: your AI builder knows your code.
Packages to update (22 packages, from 48 known issues)
Update everything with one prompt
The quickest route: one prompt that lists every package below, live-app packages first.
Step 1: paste this into your AI builder. It explains the problem first and changes nothing.
My security scan (Verilay) found known security issues in packages my app uses. Please fix them one package at a time, running the build and any tests after each one, and tell me in plain English what you changed.
Packages that ship to my users (higher priority):
- jsonwebtoken: 0.4.0 -> 9.0.0 (4 issues, critical) [major version jump: check for a same-line fix first]
- sequelize: 6.37.3 -> 6.37.8 (2 issues, critical)
- marsdb: 0.6.11 -> latest safe version (1 issue, critical)
- sanitize-html: 1.4.2 -> 2.18.0 (10 issues, high) [major version jump: check for a same-line fix first]
- js-yaml: 3.14.0 -> 3.15.2 (5 issues, high)
- @angular/router: 22.0.1 -> 22.2.1 (3 issues, high)
- lodash-es: 4.17.21 -> 4.18.0 (3 issues, high)
- @angular/common: 22.0.1 -> 22.1.1 (2 issues, high)
- body-parser: 1.20.4 -> 1.20.9 (2 issues, high)
- glob: 10.4.5 -> 14.0.2 (2 issues, high) [major version jump: check for a same-line fix first]
- compression: 1.8.1 -> 1.8.2 (1 issue, high)
- express-jwt: 0.1.3 -> 6.0.0 (1 issue, high) [major version jump: check for a same-line fix first]
- multer: 2.4.0 -> 2.5.0 (1 issue, high)
- zod: 4.4.3 -> 4.6.6 (1 issue, high)
- morgan: 1.10.0 -> 1.12.1 (3 issues, moderate)
- @angular/compiler: 22.0.1 -> 22.1.0 (1 issue, moderate)
- @angular/core: 22.0.1 -> 22.1.0 (1 issue, moderate)
- file-type: 16.5.4 -> 21.3.1 (1 issue, moderate) [major version jump: check for a same-line fix first]
- hbs: 4.2.0 -> latest safe version (1 issue, moderate)
- notevil: 1.3.3 -> latest safe version (1 issue, moderate)
Build and test tools only (lower priority, do these last):
- @cyclonedx/cyclonedx-npm: 2.0.0 -> 6.0.0 (1 issue, high) [major version jump: check for a same-line fix first]
- vitest: 4.1.1 -> 4.1.11 (1 issue, moderate)
For each package: first check whether I installed it directly or it comes in through another package. If it is indirect, update the parent package or add an `overrides` entry instead of editing node_modules. If an update is a major version jump, check for a fix inside the current major version first, and stop and ask me before making a change that breaks the build.
Please don't change anything yet. In plain English, tell me:
1. Is this really a problem? Show me the exact file and lines.
2. Who could misuse it, and what could they see or do?
3. How is this part meant to be used? What relies on it working the way it does now: other pages, a mobile app that is already released, scheduled jobs, webhooks, emails, payments or sign-in?
4. What could the fix break, and how would we avoid that?
5. How will we check afterwards that everything still works, on the website and in the mobile app if there is one?
Also check the whole app for the same kind of problem, and list every place with the file and line.
Don't change anything until I reply.
Step 2: only when its answer makes sense to you, paste this to let it make the change.
Thanks. Please fix only the place named in this report, not the other places you listed: we'll do those separately, one at a time. Keep everything you listed working. Don't publish or deploy anything. I'll test it in the preview first. Then tell me exactly what you changed, file by file, and walk me through the checks from your answer so I can confirm everything still works. If there's a mobile app that's already released, remind me to test it after publishing.
Check it yourself · about 3 minutes
Do your packages have known problems?
On GitHub, open your repository and click Security, then Dependabot alerts. It's free; if it's switched off, it can be turned on under Settings, then Security.
Or ask a developer friend to run the free command npm audit in your project folder.
✓ No high or critical alerts.
⚠ Alerts are listed. Update the packages they name, then scan again.
Updating a package can break an app, so update one at a time and test after each.
Only try this on your own app, with test accounts. Never on someone else's app.
Update jsonwebtoken 0.4.0 → 9.0.0criticalmajor version jump
4 known issues (worst: critical). Verification Bypass in jsonwebtoken
Step 1: paste this into your AI builder. It explains the problem first and changes nothing.
My security scan (Verilay) found 4 known security issues in the npm package "jsonwebtoken", which my app uses at version 0.4.0. Advisory IDs: GHSA-c7hr-j4mj-j2w6, GHSA-8cf7-32gw-wr33, GHSA-hjrf-2m68-5959, GHSA-qwph-4952-7xr6.
The fix is to use version 9.0.0 or newer.
Please:
1. Check whether "jsonwebtoken" is something I installed directly or comes in through another package (for example with `npm ls jsonwebtoken`).
2. If I installed it directly, update it to 9.0.0 or newer. If it comes in through another package, update that parent package to a version that uses a fixed "jsonwebtoken", or add an `overrides` entry in package.json. Do not edit files inside node_modules.
3. Careful: this is a jump from version 0.x to 9.x, which can break things. First check whether a fixed version exists inside the 0.x line, or whether updating the parent package solves it more safely. If the build breaks, undo the change and tell me.
4. Run the build (and any tests) and tell me in plain English what changed and whether anything stopped working.
Please don't change anything yet. In plain English, tell me:
1. Is this really a problem? Show me the exact file and lines.
2. Who could misuse it, and what could they see or do?
3. How is this part meant to be used? What relies on it working the way it does now: other pages, a mobile app that is already released, scheduled jobs, webhooks, emails, payments or sign-in?
4. What could the fix break, and how would we avoid that?
5. How will we check afterwards that everything still works, on the website and in the mobile app if there is one?
Also check the whole app for the same kind of problem, and list every place with the file and line.
Don't change anything until I reply.
Step 2: only when its answer makes sense to you, paste this to let it make the change.
Thanks. Please fix only the place named in this report, not the other places you listed: we'll do those separately, one at a time. Keep everything you listed working. Don't publish or deploy anything. I'll test it in the preview first. Then tell me exactly what you changed, file by file, and walk me through the checks from your answer so I can confirm everything still works. If there's a mobile app that's already released, remind me to test it after publishing.
Update sequelize 6.37.3 → 6.37.8critical
2 known issues (worst: critical). Sequelize: SQL Injection (Oracle DB)
Step 1: paste this into your AI builder. It explains the problem first and changes nothing.
My security scan (Verilay) found 2 known security issues in the npm package "sequelize", which my app uses at version 6.37.3. Advisory IDs: GHSA-v8fg-2rw7-q452, GHSA-6457-6jrx-69cr.
The fix is to use version 6.37.8 or newer.
Please:
1. Check whether "sequelize" is something I installed directly or comes in through another package (for example with `npm ls sequelize`).
2. If I installed it directly, update it to 6.37.8 or newer. If it comes in through another package, update that parent package to a version that uses a fixed "sequelize", or add an `overrides` entry in package.json. Do not edit files inside node_modules.
3. Run the build (and any tests) and tell me in plain English what changed and whether anything stopped working.
Please don't change anything yet. In plain English, tell me:
1. Is this really a problem? Show me the exact file and lines.
2. Who could misuse it, and what could they see or do?
3. How is this part meant to be used? What relies on it working the way it does now: other pages, a mobile app that is already released, scheduled jobs, webhooks, emails, payments or sign-in?
4. What could the fix break, and how would we avoid that?
5. How will we check afterwards that everything still works, on the website and in the mobile app if there is one?
Also check the whole app for the same kind of problem, and list every place with the file and line.
Don't change anything until I reply.
Step 2: only when its answer makes sense to you, paste this to let it make the change.
Thanks. Please fix only the place named in this report, not the other places you listed: we'll do those separately, one at a time. Keep everything you listed working. Don't publish or deploy anything. I'll test it in the preview first. Then tell me exactly what you changed, file by file, and walk me through the checks from your answer so I can confirm everything still works. If there's a mobile app that's already released, remind me to test it after publishing.
marsdb 0.6.11: no fixed version listedcritical
1 known issue (worst: critical). Command Injection in marsdb
Step 1: paste this into your AI builder. It explains the problem first and changes nothing.
My security scan (Verilay) found 1 known security issue in the npm package "marsdb", which my app uses at version 0.6.11. Advisory IDs: GHSA-5mrr-rgp6-x4gr.
No fixed version is listed yet, so please check the latest available version and whether there is a safe alternative.
Please:
1. Check whether "marsdb" is something I installed directly or comes in through another package (for example with `npm ls marsdb`).
2. If I installed it directly, update it to the latest safe version. If it comes in through another package, update that parent package to a version that uses a fixed "marsdb", or add an `overrides` entry in package.json. Do not edit files inside node_modules.
3. Run the build (and any tests) and tell me in plain English what changed and whether anything stopped working.
Please don't change anything yet. In plain English, tell me:
1. Is this really a problem? Show me the exact file and lines.
2. Who could misuse it, and what could they see or do?
3. How is this part meant to be used? What relies on it working the way it does now: other pages, a mobile app that is already released, scheduled jobs, webhooks, emails, payments or sign-in?
4. What could the fix break, and how would we avoid that?
5. How will we check afterwards that everything still works, on the website and in the mobile app if there is one?
Also check the whole app for the same kind of problem, and list every place with the file and line.
Don't change anything until I reply.
Step 2: only when its answer makes sense to you, paste this to let it make the change.
Thanks. Please fix only the place named in this report, not the other places you listed: we'll do those separately, one at a time. Keep everything you listed working. Don't publish or deploy anything. I'll test it in the preview first. Then tell me exactly what you changed, file by file, and walk me through the checks from your answer so I can confirm everything still works. If there's a mobile app that's already released, remind me to test it after publishing.
Update sanitize-html 1.4.2 → 2.18.0highmajor version jump
10 known issues (worst: high). Sanitize-html Vulnerable To REDoS Attacks
Step 1: paste this into your AI builder. It explains the problem first and changes nothing.
My security scan (Verilay) found 10 known security issues in the npm package "sanitize-html", which my app uses at version 1.4.2. Advisory IDs: GHSA-cgfm-xwp7-2cvr, GHSA-3j7m-hmh3-9jmp, GHSA-cv27-6wvh-8x7j, GHSA-jxwj-j7wr-gfrw, GHSA-mjxr-4v3x-q3m4, GHSA-qhxp-v273-g94h and 4 more.
The fix is to use version 2.18.0 or newer.
Please:
1. Check whether "sanitize-html" is something I installed directly or comes in through another package (for example with `npm ls sanitize-html`).
2. If I installed it directly, update it to 2.18.0 or newer. If it comes in through another package, update that parent package to a version that uses a fixed "sanitize-html", or add an `overrides` entry in package.json. Do not edit files inside node_modules.
3. Careful: this is a jump from version 1.x to 2.x, which can break things. First check whether a fixed version exists inside the 1.x line, or whether updating the parent package solves it more safely. If the build breaks, undo the change and tell me.
4. Run the build (and any tests) and tell me in plain English what changed and whether anything stopped working.
Please don't change anything yet. In plain English, tell me:
1. Is this really a problem? Show me the exact file and lines.
2. Who could misuse it, and what could they see or do?
3. How is this part meant to be used? What relies on it working the way it does now: other pages, a mobile app that is already released, scheduled jobs, webhooks, emails, payments or sign-in?
4. What could the fix break, and how would we avoid that?
5. How will we check afterwards that everything still works, on the website and in the mobile app if there is one?
Also check the whole app for the same kind of problem, and list every place with the file and line.
Don't change anything until I reply.
Step 2: only when its answer makes sense to you, paste this to let it make the change.
Thanks. Please fix only the place named in this report, not the other places you listed: we'll do those separately, one at a time. Keep everything you listed working. Don't publish or deploy anything. I'll test it in the preview first. Then tell me exactly what you changed, file by file, and walk me through the checks from your answer so I can confirm everything still works. If there's a mobile app that's already released, remind me to test it after publishing.
Update js-yaml 3.14.0 → 3.15.2high
5 known issues (worst: high). js-yaml: maxTotalMergeKeys does not limit CPU use for empty merge sources
Step 1: paste this into your AI builder. It explains the problem first and changes nothing.
My security scan (Verilay) found 5 known security issues in the npm package "js-yaml", which my app uses at version 3.14.0. Advisory IDs: GHSA-2883-xcg3-v3hh, GHSA-52cp-r559-cp3m, GHSA-5p4m-2wfm-xmqj, GHSA-h67p-54hq-rp68, GHSA-mh29-5h37-fv8m.
The fix is to use version 3.15.2 or newer.
Please:
1. Check whether "js-yaml" is something I installed directly or comes in through another package (for example with `npm ls js-yaml`).
2. If I installed it directly, update it to 3.15.2 or newer. If it comes in through another package, update that parent package to a version that uses a fixed "js-yaml", or add an `overrides` entry in package.json. Do not edit files inside node_modules.
3. Run the build (and any tests) and tell me in plain English what changed and whether anything stopped working.
Please don't change anything yet. In plain English, tell me:
1. Is this really a problem? Show me the exact file and lines.
2. Who could misuse it, and what could they see or do?
3. How is this part meant to be used? What relies on it working the way it does now: other pages, a mobile app that is already released, scheduled jobs, webhooks, emails, payments or sign-in?
4. What could the fix break, and how would we avoid that?
5. How will we check afterwards that everything still works, on the website and in the mobile app if there is one?
Also check the whole app for the same kind of problem, and list every place with the file and line.
Don't change anything until I reply.
Step 2: only when its answer makes sense to you, paste this to let it make the change.
Thanks. Please fix only the place named in this report, not the other places you listed: we'll do those separately, one at a time. Keep everything you listed working. Don't publish or deploy anything. I'll test it in the preview first. Then tell me exactly what you changed, file by file, and walk me through the checks from your answer so I can confirm everything still works. If there's a mobile app that's already released, remind me to test it after publishing.
Update @angular/router 22.0.1 → 22.2.1high
3 known issues (worst: high). @angular/router: Denial of Service via RouterLink Query Parameter Retention in Server-Side Rendering (SSR)
Step 1: paste this into your AI builder. It explains the problem first and changes nothing.
My security scan (Verilay) found 3 known security issues in the npm package "@angular/router", which my app uses at version 22.0.1. Advisory IDs: GHSA-57xq-rjx2-v5xh, GHSA-62vg-58rm-qff7, GHSA-ff3f-86qr-9cv3.
The fix is to use version 22.2.1 or newer.
Please:
1. Check whether "@angular/router" is something I installed directly or comes in through another package (for example with `npm ls @angular/router`).
2. If I installed it directly, update it to 22.2.1 or newer. If it comes in through another package, update that parent package to a version that uses a fixed "@angular/router", or add an `overrides` entry in package.json. Do not edit files inside node_modules.
3. Run the build (and any tests) and tell me in plain English what changed and whether anything stopped working.
Please don't change anything yet. In plain English, tell me:
1. Is this really a problem? Show me the exact file and lines.
2. Who could misuse it, and what could they see or do?
3. How is this part meant to be used? What relies on it working the way it does now: other pages, a mobile app that is already released, scheduled jobs, webhooks, emails, payments or sign-in?
4. What could the fix break, and how would we avoid that?
5. How will we check afterwards that everything still works, on the website and in the mobile app if there is one?
Also check the whole app for the same kind of problem, and list every place with the file and line.
Don't change anything until I reply.
Step 2: only when its answer makes sense to you, paste this to let it make the change.
Thanks. Please fix only the place named in this report, not the other places you listed: we'll do those separately, one at a time. Keep everything you listed working. Don't publish or deploy anything. I'll test it in the preview first. Then tell me exactly what you changed, file by file, and walk me through the checks from your answer so I can confirm everything still works. If there's a mobile app that's already released, remind me to test it after publishing.
Update lodash-es 4.17.21 → 4.18.0high
3 known issues (worst: high). lodash vulnerable to Code Injection via `_.template` imports key names
Step 1: paste this into your AI builder. It explains the problem first and changes nothing.
My security scan (Verilay) found 3 known security issues in the npm package "lodash-es", which my app uses at version 4.17.21. Advisory IDs: GHSA-r5fr-rjxr-66jc, GHSA-f23m-r3pf-42rh, GHSA-xxjr-mmjv-4gpg.
The fix is to use version 4.18.0 or newer.
Please:
1. Check whether "lodash-es" is something I installed directly or comes in through another package (for example with `npm ls lodash-es`).
2. If I installed it directly, update it to 4.18.0 or newer. If it comes in through another package, update that parent package to a version that uses a fixed "lodash-es", or add an `overrides` entry in package.json. Do not edit files inside node_modules.
3. Run the build (and any tests) and tell me in plain English what changed and whether anything stopped working.
Please don't change anything yet. In plain English, tell me:
1. Is this really a problem? Show me the exact file and lines.
2. Who could misuse it, and what could they see or do?
3. How is this part meant to be used? What relies on it working the way it does now: other pages, a mobile app that is already released, scheduled jobs, webhooks, emails, payments or sign-in?
4. What could the fix break, and how would we avoid that?
5. How will we check afterwards that everything still works, on the website and in the mobile app if there is one?
Also check the whole app for the same kind of problem, and list every place with the file and line.
Don't change anything until I reply.
Step 2: only when its answer makes sense to you, paste this to let it make the change.
Thanks. Please fix only the place named in this report, not the other places you listed: we'll do those separately, one at a time. Keep everything you listed working. Don't publish or deploy anything. I'll test it in the preview first. Then tell me exactly what you changed, file by file, and walk me through the checks from your answer so I can confirm everything still works. If there's a mobile app that's already released, remind me to test it after publishing.
Update @angular/common 22.0.1 → 22.1.1high
2 known issues (worst: high). Angular: Cache-Key Ambiguity in HttpTransferCache Leading to Cross-Request Response Reuse and State Poisoning
Step 1: paste this into your AI builder. It explains the problem first and changes nothing.
My security scan (Verilay) found 2 known security issues in the npm package "@angular/common", which my app uses at version 22.0.1. Advisory IDs: GHSA-jhpw-976m-542j, GHSA-p297-fm68-3q8c.
The fix is to use version 22.1.1 or newer.
Please:
1. Check whether "@angular/common" is something I installed directly or comes in through another package (for example with `npm ls @angular/common`).
2. If I installed it directly, update it to 22.1.1 or newer. If it comes in through another package, update that parent package to a version that uses a fixed "@angular/common", or add an `overrides` entry in package.json. Do not edit files inside node_modules.
3. Run the build (and any tests) and tell me in plain English what changed and whether anything stopped working.
Please don't change anything yet. In plain English, tell me:
1. Is this really a problem? Show me the exact file and lines.
2. Who could misuse it, and what could they see or do?
3. How is this part meant to be used? What relies on it working the way it does now: other pages, a mobile app that is already released, scheduled jobs, webhooks, emails, payments or sign-in?
4. What could the fix break, and how would we avoid that?
5. How will we check afterwards that everything still works, on the website and in the mobile app if there is one?
Also check the whole app for the same kind of problem, and list every place with the file and line.
Don't change anything until I reply.
Step 2: only when its answer makes sense to you, paste this to let it make the change.
Thanks. Please fix only the place named in this report, not the other places you listed: we'll do those separately, one at a time. Keep everything you listed working. Don't publish or deploy anything. I'll test it in the preview first. Then tell me exactly what you changed, file by file, and walk me through the checks from your answer so I can confirm everything still works. If there's a mobile app that's already released, remind me to test it after publishing.
Update body-parser 1.20.4 → 1.20.9high
2 known issues (worst: high). body-parser vulnerable to Denial of Service via trailing bytes after a compressed request body
Step 1: paste this into your AI builder. It explains the problem first and changes nothing.
My security scan (Verilay) found 2 known security issues in the npm package "body-parser", which my app uses at version 1.20.4. Advisory IDs: GHSA-27r3-jxmh-p828, GHSA-v422-hmwv-36x6.
The fix is to use version 1.20.9 or newer.
Please:
1. Check whether "body-parser" is something I installed directly or comes in through another package (for example with `npm ls body-parser`).
2. If I installed it directly, update it to 1.20.9 or newer. If it comes in through another package, update that parent package to a version that uses a fixed "body-parser", or add an `overrides` entry in package.json. Do not edit files inside node_modules.
3. Run the build (and any tests) and tell me in plain English what changed and whether anything stopped working.
Please don't change anything yet. In plain English, tell me:
1. Is this really a problem? Show me the exact file and lines.
2. Who could misuse it, and what could they see or do?
3. How is this part meant to be used? What relies on it working the way it does now: other pages, a mobile app that is already released, scheduled jobs, webhooks, emails, payments or sign-in?
4. What could the fix break, and how would we avoid that?
5. How will we check afterwards that everything still works, on the website and in the mobile app if there is one?
Also check the whole app for the same kind of problem, and list every place with the file and line.
Don't change anything until I reply.
Step 2: only when its answer makes sense to you, paste this to let it make the change.
Thanks. Please fix only the place named in this report, not the other places you listed: we'll do those separately, one at a time. Keep everything you listed working. Don't publish or deploy anything. I'll test it in the preview first. Then tell me exactly what you changed, file by file, and walk me through the checks from your answer so I can confirm everything still works. If there's a mobile app that's already released, remind me to test it after publishing.
Update glob 10.4.5 → 14.0.2highmajor version jump
2 known issues (worst: high). glob CLI: Command injection via -c/--cmd executes matches with shell:true
Step 1: paste this into your AI builder. It explains the problem first and changes nothing.
My security scan (Verilay) found 2 known security issues in the npm package "glob", which my app uses at version 10.4.5. Advisory IDs: GHSA-5j98-mcp5-4vw2, GHSA-3g3m-2fjr-6pw4.
The fix is to use version 14.0.2 or newer.
Please:
1. Check whether "glob" is something I installed directly or comes in through another package (for example with `npm ls glob`).
2. If I installed it directly, update it to 14.0.2 or newer. If it comes in through another package, update that parent package to a version that uses a fixed "glob", or add an `overrides` entry in package.json. Do not edit files inside node_modules.
3. Careful: this is a jump from version 10.x to 14.x, which can break things. First check whether a fixed version exists inside the 10.x line, or whether updating the parent package solves it more safely. If the build breaks, undo the change and tell me.
4. Run the build (and any tests) and tell me in plain English what changed and whether anything stopped working.
Please don't change anything yet. In plain English, tell me:
1. Is this really a problem? Show me the exact file and lines.
2. Who could misuse it, and what could they see or do?
3. How is this part meant to be used? What relies on it working the way it does now: other pages, a mobile app that is already released, scheduled jobs, webhooks, emails, payments or sign-in?
4. What could the fix break, and how would we avoid that?
5. How will we check afterwards that everything still works, on the website and in the mobile app if there is one?
Also check the whole app for the same kind of problem, and list every place with the file and line.
Don't change anything until I reply.
Step 2: only when its answer makes sense to you, paste this to let it make the change.
Thanks. Please fix only the place named in this report, not the other places you listed: we'll do those separately, one at a time. Keep everything you listed working. Don't publish or deploy anything. I'll test it in the preview first. Then tell me exactly what you changed, file by file, and walk me through the checks from your answer so I can confirm everything still works. If there's a mobile app that's already released, remind me to test it after publishing.
Update compression 1.8.1 → 1.8.2high
1 known issue (worst: high). compression vulnerable to Denial of Service via memory leak on premature response close
Step 1: paste this into your AI builder. It explains the problem first and changes nothing.
My security scan (Verilay) found 1 known security issue in the npm package "compression", which my app uses at version 1.8.1. Advisory IDs: GHSA-vc2v-76pw-4v95.
The fix is to use version 1.8.2 or newer.
Please:
1. Check whether "compression" is something I installed directly or comes in through another package (for example with `npm ls compression`).
2. If I installed it directly, update it to 1.8.2 or newer. If it comes in through another package, update that parent package to a version that uses a fixed "compression", or add an `overrides` entry in package.json. Do not edit files inside node_modules.
3. Run the build (and any tests) and tell me in plain English what changed and whether anything stopped working.
Please don't change anything yet. In plain English, tell me:
1. Is this really a problem? Show me the exact file and lines.
2. Who could misuse it, and what could they see or do?
3. How is this part meant to be used? What relies on it working the way it does now: other pages, a mobile app that is already released, scheduled jobs, webhooks, emails, payments or sign-in?
4. What could the fix break, and how would we avoid that?
5. How will we check afterwards that everything still works, on the website and in the mobile app if there is one?
Also check the whole app for the same kind of problem, and list every place with the file and line.
Don't change anything until I reply.
Step 2: only when its answer makes sense to you, paste this to let it make the change.
Thanks. Please fix only the place named in this report, not the other places you listed: we'll do those separately, one at a time. Keep everything you listed working. Don't publish or deploy anything. I'll test it in the preview first. Then tell me exactly what you changed, file by file, and walk me through the checks from your answer so I can confirm everything still works. If there's a mobile app that's already released, remind me to test it after publishing.
Update express-jwt 0.1.3 → 6.0.0highmajor version jump
1 known issue (worst: high). Authorization bypass in express-jwt
Step 1: paste this into your AI builder. It explains the problem first and changes nothing.
My security scan (Verilay) found 1 known security issue in the npm package "express-jwt", which my app uses at version 0.1.3. Advisory IDs: GHSA-6g6m-m6h5-w9gf.
The fix is to use version 6.0.0 or newer.
Please:
1. Check whether "express-jwt" is something I installed directly or comes in through another package (for example with `npm ls express-jwt`).
2. If I installed it directly, update it to 6.0.0 or newer. If it comes in through another package, update that parent package to a version that uses a fixed "express-jwt", or add an `overrides` entry in package.json. Do not edit files inside node_modules.
3. Careful: this is a jump from version 0.x to 6.x, which can break things. First check whether a fixed version exists inside the 0.x line, or whether updating the parent package solves it more safely. If the build breaks, undo the change and tell me.
4. Run the build (and any tests) and tell me in plain English what changed and whether anything stopped working.
Please don't change anything yet. In plain English, tell me:
1. Is this really a problem? Show me the exact file and lines.
2. Who could misuse it, and what could they see or do?
3. How is this part meant to be used? What relies on it working the way it does now: other pages, a mobile app that is already released, scheduled jobs, webhooks, emails, payments or sign-in?
4. What could the fix break, and how would we avoid that?
5. How will we check afterwards that everything still works, on the website and in the mobile app if there is one?
Also check the whole app for the same kind of problem, and list every place with the file and line.
Don't change anything until I reply.
Step 2: only when its answer makes sense to you, paste this to let it make the change.
Thanks. Please fix only the place named in this report, not the other places you listed: we'll do those separately, one at a time. Keep everything you listed working. Don't publish or deploy anything. I'll test it in the preview first. Then tell me exactly what you changed, file by file, and walk me through the checks from your answer so I can confirm everything still works. If there's a mobile app that's already released, remind me to test it after publishing.
Update multer 2.4.0 → 2.5.0high
1 known issue (worst: high). multer vulnerable to Denial of Service via a pending asynchronous fileFilter after request teardown
Step 1: paste this into your AI builder. It explains the problem first and changes nothing.
My security scan (Verilay) found 1 known security issue in the npm package "multer", which my app uses at version 2.4.0. Advisory IDs: GHSA-q7qp-rjg7-q26m.
The fix is to use version 2.5.0 or newer.
Please:
1. Check whether "multer" is something I installed directly or comes in through another package (for example with `npm ls multer`).
2. If I installed it directly, update it to 2.5.0 or newer. If it comes in through another package, update that parent package to a version that uses a fixed "multer", or add an `overrides` entry in package.json. Do not edit files inside node_modules.
3. Run the build (and any tests) and tell me in plain English what changed and whether anything stopped working.
Please don't change anything yet. In plain English, tell me:
1. Is this really a problem? Show me the exact file and lines.
2. Who could misuse it, and what could they see or do?
3. How is this part meant to be used? What relies on it working the way it does now: other pages, a mobile app that is already released, scheduled jobs, webhooks, emails, payments or sign-in?
4. What could the fix break, and how would we avoid that?
5. How will we check afterwards that everything still works, on the website and in the mobile app if there is one?
Also check the whole app for the same kind of problem, and list every place with the file and line.
Don't change anything until I reply.
Step 2: only when its answer makes sense to you, paste this to let it make the change.
Thanks. Please fix only the place named in this report, not the other places you listed: we'll do those separately, one at a time. Keep everything you listed working. Don't publish or deploy anything. I'll test it in the preview first. Then tell me exactly what you changed, file by file, and walk me through the checks from your answer so I can confirm everything still works. If there's a mobile app that's already released, remind me to test it after publishing.
Update zod 4.4.3 → 4.6.6high
1 known issue (worst: high). Zod can exhaust memory while validating oversized constrained collections
Step 1: paste this into your AI builder. It explains the problem first and changes nothing.
My security scan (Verilay) found 1 known security issue in the npm package "zod", which my app uses at version 4.4.3. Advisory IDs: GHSA-mrhx-c7xc-m3w5.
The fix is to use version 4.6.6 or newer.
Please:
1. Check whether "zod" is something I installed directly or comes in through another package (for example with `npm ls zod`).
2. If I installed it directly, update it to 4.6.6 or newer. If it comes in through another package, update that parent package to a version that uses a fixed "zod", or add an `overrides` entry in package.json. Do not edit files inside node_modules.
3. Run the build (and any tests) and tell me in plain English what changed and whether anything stopped working.
Please don't change anything yet. In plain English, tell me:
1. Is this really a problem? Show me the exact file and lines.
2. Who could misuse it, and what could they see or do?
3. How is this part meant to be used? What relies on it working the way it does now: other pages, a mobile app that is already released, scheduled jobs, webhooks, emails, payments or sign-in?
4. What could the fix break, and how would we avoid that?
5. How will we check afterwards that everything still works, on the website and in the mobile app if there is one?
Also check the whole app for the same kind of problem, and list every place with the file and line.
Don't change anything until I reply.
Step 2: only when its answer makes sense to you, paste this to let it make the change.
Thanks. Please fix only the place named in this report, not the other places you listed: we'll do those separately, one at a time. Keep everything you listed working. Don't publish or deploy anything. I'll test it in the preview first. Then tell me exactly what you changed, file by file, and walk me through the checks from your answer so I can confirm everything still works. If there's a mobile app that's already released, remind me to test it after publishing.
Update morgan 1.10.0 → 1.12.1moderate
3 known issues (worst: moderate). morgan vulnerable to Log Forging via unneutralized control characters in :remote-user
Step 1: paste this into your AI builder. It explains the problem first and changes nothing.
My security scan (Verilay) found 3 known security issues in the npm package "morgan", which my app uses at version 1.10.0. Advisory IDs: GHSA-4vj7-5mj6-jm8m, GHSA-9f6g-j8ch-79g4, GHSA-jxfw-x594-9x9m.
The fix is to use version 1.12.1 or newer.
Please:
1. Check whether "morgan" is something I installed directly or comes in through another package (for example with `npm ls morgan`).
2. If I installed it directly, update it to 1.12.1 or newer. If it comes in through another package, update that parent package to a version that uses a fixed "morgan", or add an `overrides` entry in package.json. Do not edit files inside node_modules.
3. Run the build (and any tests) and tell me in plain English what changed and whether anything stopped working.
Please don't change anything yet. In plain English, tell me:
1. Is this really a problem? Show me the exact file and lines.
2. Who could misuse it, and what could they see or do?
3. How is this part meant to be used? What relies on it working the way it does now: other pages, a mobile app that is already released, scheduled jobs, webhooks, emails, payments or sign-in?
4. What could the fix break, and how would we avoid that?
5. How will we check afterwards that everything still works, on the website and in the mobile app if there is one?
Also check the whole app for the same kind of problem, and list every place with the file and line.
Don't change anything until I reply.
Step 2: only when its answer makes sense to you, paste this to let it make the change.
Thanks. Please fix only the place named in this report, not the other places you listed: we'll do those separately, one at a time. Keep everything you listed working. Don't publish or deploy anything. I'll test it in the preview first. Then tell me exactly what you changed, file by file, and walk me through the checks from your answer so I can confirm everything still works. If there's a mobile app that's already released, remind me to test it after publishing.
Update @angular/compiler 22.0.1 → 22.1.0moderate
1 known issue (worst: moderate). Angular: Sanitization bypass via directive host bindings on concrete host elements in @angular/core and @angular/compiler
Step 1: paste this into your AI builder. It explains the problem first and changes nothing.
My security scan (Verilay) found 1 known security issue in the npm package "@angular/compiler", which my app uses at version 22.0.1. Advisory IDs: GHSA-hh8m-fm6v-7cvg.
The fix is to use version 22.1.0 or newer.
Please:
1. Check whether "@angular/compiler" is something I installed directly or comes in through another package (for example with `npm ls @angular/compiler`).
2. If I installed it directly, update it to 22.1.0 or newer. If it comes in through another package, update that parent package to a version that uses a fixed "@angular/compiler", or add an `overrides` entry in package.json. Do not edit files inside node_modules.
3. Run the build (and any tests) and tell me in plain English what changed and whether anything stopped working.
Please don't change anything yet. In plain English, tell me:
1. Is this really a problem? Show me the exact file and lines.
2. Who could misuse it, and what could they see or do?
3. How is this part meant to be used? What relies on it working the way it does now: other pages, a mobile app that is already released, scheduled jobs, webhooks, emails, payments or sign-in?
4. What could the fix break, and how would we avoid that?
5. How will we check afterwards that everything still works, on the website and in the mobile app if there is one?
Also check the whole app for the same kind of problem, and list every place with the file and line.
Don't change anything until I reply.
Step 2: only when its answer makes sense to you, paste this to let it make the change.
Thanks. Please fix only the place named in this report, not the other places you listed: we'll do those separately, one at a time. Keep everything you listed working. Don't publish or deploy anything. I'll test it in the preview first. Then tell me exactly what you changed, file by file, and walk me through the checks from your answer so I can confirm everything still works. If there's a mobile app that's already released, remind me to test it after publishing.
Update @angular/core 22.0.1 → 22.1.0moderate
1 known issue (worst: moderate). Angular: Sanitization bypass via directive host bindings on concrete host elements in @angular/core and @angular/compiler
Step 1: paste this into your AI builder. It explains the problem first and changes nothing.
My security scan (Verilay) found 1 known security issue in the npm package "@angular/core", which my app uses at version 22.0.1. Advisory IDs: GHSA-hh8m-fm6v-7cvg.
The fix is to use version 22.1.0 or newer.
Please:
1. Check whether "@angular/core" is something I installed directly or comes in through another package (for example with `npm ls @angular/core`).
2. If I installed it directly, update it to 22.1.0 or newer. If it comes in through another package, update that parent package to a version that uses a fixed "@angular/core", or add an `overrides` entry in package.json. Do not edit files inside node_modules.
3. Run the build (and any tests) and tell me in plain English what changed and whether anything stopped working.
Please don't change anything yet. In plain English, tell me:
1. Is this really a problem? Show me the exact file and lines.
2. Who could misuse it, and what could they see or do?
3. How is this part meant to be used? What relies on it working the way it does now: other pages, a mobile app that is already released, scheduled jobs, webhooks, emails, payments or sign-in?
4. What could the fix break, and how would we avoid that?
5. How will we check afterwards that everything still works, on the website and in the mobile app if there is one?
Also check the whole app for the same kind of problem, and list every place with the file and line.
Don't change anything until I reply.
Step 2: only when its answer makes sense to you, paste this to let it make the change.
Thanks. Please fix only the place named in this report, not the other places you listed: we'll do those separately, one at a time. Keep everything you listed working. Don't publish or deploy anything. I'll test it in the preview first. Then tell me exactly what you changed, file by file, and walk me through the checks from your answer so I can confirm everything still works. If there's a mobile app that's already released, remind me to test it after publishing.
Update file-type 16.5.4 → 21.3.1moderatemajor version jump
1 known issue (worst: moderate). file-type affected by infinite loop in ASF parser on malformed input with zero-size sub-header
Step 1: paste this into your AI builder. It explains the problem first and changes nothing.
My security scan (Verilay) found 1 known security issue in the npm package "file-type", which my app uses at version 16.5.4. Advisory IDs: GHSA-5v7r-6r5c-r473.
The fix is to use version 21.3.1 or newer.
Please:
1. Check whether "file-type" is something I installed directly or comes in through another package (for example with `npm ls file-type`).
2. If I installed it directly, update it to 21.3.1 or newer. If it comes in through another package, update that parent package to a version that uses a fixed "file-type", or add an `overrides` entry in package.json. Do not edit files inside node_modules.
3. Careful: this is a jump from version 16.x to 21.x, which can break things. First check whether a fixed version exists inside the 16.x line, or whether updating the parent package solves it more safely. If the build breaks, undo the change and tell me.
4. Run the build (and any tests) and tell me in plain English what changed and whether anything stopped working.
Please don't change anything yet. In plain English, tell me:
1. Is this really a problem? Show me the exact file and lines.
2. Who could misuse it, and what could they see or do?
3. How is this part meant to be used? What relies on it working the way it does now: other pages, a mobile app that is already released, scheduled jobs, webhooks, emails, payments or sign-in?
4. What could the fix break, and how would we avoid that?
5. How will we check afterwards that everything still works, on the website and in the mobile app if there is one?
Also check the whole app for the same kind of problem, and list every place with the file and line.
Don't change anything until I reply.
Step 2: only when its answer makes sense to you, paste this to let it make the change.
Thanks. Please fix only the place named in this report, not the other places you listed: we'll do those separately, one at a time. Keep everything you listed working. Don't publish or deploy anything. I'll test it in the preview first. Then tell me exactly what you changed, file by file, and walk me through the checks from your answer so I can confirm everything still works. If there's a mobile app that's already released, remind me to test it after publishing.
hbs 4.2.0: no fixed version listedmoderate
1 known issue (worst: moderate). hbs: Insertion of Sensitive Information into Externally-Accessible File or Directory and Exposure of Sensitive Information to an Unauthorized Actor
Step 1: paste this into your AI builder. It explains the problem first and changes nothing.
My security scan (Verilay) found 1 known security issue in the npm package "hbs", which my app uses at version 4.2.0. Advisory IDs: GHSA-7f5c-rpf4-86p8.
No fixed version is listed yet, so please check the latest available version and whether there is a safe alternative.
Please:
1. Check whether "hbs" is something I installed directly or comes in through another package (for example with `npm ls hbs`).
2. If I installed it directly, update it to the latest safe version. If it comes in through another package, update that parent package to a version that uses a fixed "hbs", or add an `overrides` entry in package.json. Do not edit files inside node_modules.
3. Run the build (and any tests) and tell me in plain English what changed and whether anything stopped working.
Please don't change anything yet. In plain English, tell me:
1. Is this really a problem? Show me the exact file and lines.
2. Who could misuse it, and what could they see or do?
3. How is this part meant to be used? What relies on it working the way it does now: other pages, a mobile app that is already released, scheduled jobs, webhooks, emails, payments or sign-in?
4. What could the fix break, and how would we avoid that?
5. How will we check afterwards that everything still works, on the website and in the mobile app if there is one?
Also check the whole app for the same kind of problem, and list every place with the file and line.
Don't change anything until I reply.
Step 2: only when its answer makes sense to you, paste this to let it make the change.
Thanks. Please fix only the place named in this report, not the other places you listed: we'll do those separately, one at a time. Keep everything you listed working. Don't publish or deploy anything. I'll test it in the preview first. Then tell me exactly what you changed, file by file, and walk me through the checks from your answer so I can confirm everything still works. If there's a mobile app that's already released, remind me to test it after publishing.
notevil 1.3.3: no fixed version listedmoderate
1 known issue (worst: moderate). Sandbox escape in notevil and argencoders-notevil
Step 1: paste this into your AI builder. It explains the problem first and changes nothing.
My security scan (Verilay) found 1 known security issue in the npm package "notevil", which my app uses at version 1.3.3. Advisory IDs: GHSA-8g4m-cjm2-96wq.
No fixed version is listed yet, so please check the latest available version and whether there is a safe alternative.
Please:
1. Check whether "notevil" is something I installed directly or comes in through another package (for example with `npm ls notevil`).
2. If I installed it directly, update it to the latest safe version. If it comes in through another package, update that parent package to a version that uses a fixed "notevil", or add an `overrides` entry in package.json. Do not edit files inside node_modules.
3. Run the build (and any tests) and tell me in plain English what changed and whether anything stopped working.
Please don't change anything yet. In plain English, tell me:
1. Is this really a problem? Show me the exact file and lines.
2. Who could misuse it, and what could they see or do?
3. How is this part meant to be used? What relies on it working the way it does now: other pages, a mobile app that is already released, scheduled jobs, webhooks, emails, payments or sign-in?
4. What could the fix break, and how would we avoid that?
5. How will we check afterwards that everything still works, on the website and in the mobile app if there is one?
Also check the whole app for the same kind of problem, and list every place with the file and line.
Don't change anything until I reply.
Step 2: only when its answer makes sense to you, paste this to let it make the change.
Thanks. Please fix only the place named in this report, not the other places you listed: we'll do those separately, one at a time. Keep everything you listed working. Don't publish or deploy anything. I'll test it in the preview first. Then tell me exactly what you changed, file by file, and walk me through the checks from your answer so I can confirm everything still works. If there's a mobile app that's already released, remind me to test it after publishing.
Build and test tools only (2): not shipped to your users, so lower priority
Update @cyclonedx/cyclonedx-npm 2.0.0 → 6.0.0dev toolmajor version jump
1 known issue (worst: high). @cyclonedx/cyclonedx-npm: Shell Injection via Unsanitized --workspace Argument on Windows This is a build/test tool, not shipped to your users, so it is lower priority.
Step 1: paste this into your AI builder. It explains the problem first and changes nothing.
My security scan (Verilay) found 1 known security issue in the npm package "@cyclonedx/cyclonedx-npm", which my app uses at version 2.0.0. Advisory IDs: GHSA-q69g-4hcv-6jg4.
The fix is to use version 6.0.0 or newer.
Please:
1. Check whether "@cyclonedx/cyclonedx-npm" is something I installed directly or comes in through another package (for example with `npm ls @cyclonedx/cyclonedx-npm`).
2. If I installed it directly, update it to 6.0.0 or newer. If it comes in through another package, update that parent package to a version that uses a fixed "@cyclonedx/cyclonedx-npm", or add an `overrides` entry in package.json. Do not edit files inside node_modules.
3. Careful: this is a jump from version 2.x to 6.x, which can break things. First check whether a fixed version exists inside the 2.x line, or whether updating the parent package solves it more safely. If the build breaks, undo the change and tell me.
4. Run the build (and any tests) and tell me in plain English what changed and whether anything stopped working.
Note: this is a development/build tool, not part of what my visitors use, so treat it as lower priority than packages that ship to users.
Please don't change anything yet. In plain English, tell me:
1. Is this really a problem? Show me the exact file and lines.
2. Who could misuse it, and what could they see or do?
3. How is this part meant to be used? What relies on it working the way it does now: other pages, a mobile app that is already released, scheduled jobs, webhooks, emails, payments or sign-in?
4. What could the fix break, and how would we avoid that?
5. How will we check afterwards that everything still works, on the website and in the mobile app if there is one?
Also check the whole app for the same kind of problem, and list every place with the file and line.
Don't change anything until I reply.
Step 2: only when its answer makes sense to you, paste this to let it make the change.
Thanks. Please fix only the place named in this report, not the other places you listed: we'll do those separately, one at a time. Keep everything you listed working. Don't publish or deploy anything. I'll test it in the preview first. Then tell me exactly what you changed, file by file, and walk me through the checks from your answer so I can confirm everything still works. If there's a mobile app that's already released, remind me to test it after publishing.
Update vitest 4.1.1 → 4.1.11dev tool
1 known issue (worst: moderate). Vitest: Path Traversal / Arbitrary File Read via @vitest/mocker Redirect Mock This is a build/test tool, not shipped to your users, so it is lower priority.
Step 1: paste this into your AI builder. It explains the problem first and changes nothing.
My security scan (Verilay) found 1 known security issue in the npm package "vitest", which my app uses at version 4.1.1. Advisory IDs: GHSA-82fw-gwwq-j7x9.
The fix is to use version 4.1.11 or newer.
Please:
1. Check whether "vitest" is something I installed directly or comes in through another package (for example with `npm ls vitest`).
2. If I installed it directly, update it to 4.1.11 or newer. If it comes in through another package, update that parent package to a version that uses a fixed "vitest", or add an `overrides` entry in package.json. Do not edit files inside node_modules.
3. Run the build (and any tests) and tell me in plain English what changed and whether anything stopped working.
Note: this is a development/build tool, not part of what my visitors use, so treat it as lower priority than packages that ship to users.
Please don't change anything yet. In plain English, tell me:
1. Is this really a problem? Show me the exact file and lines.
2. Who could misuse it, and what could they see or do?
3. How is this part meant to be used? What relies on it working the way it does now: other pages, a mobile app that is already released, scheduled jobs, webhooks, emails, payments or sign-in?
4. What could the fix break, and how would we avoid that?
5. How will we check afterwards that everything still works, on the website and in the mobile app if there is one?
Also check the whole app for the same kind of problem, and list every place with the file and line.
Don't change anything until I reply.
Step 2: only when its answer makes sense to you, paste this to let it make the change.
Thanks. Please fix only the place named in this report, not the other places you listed: we'll do those separately, one at a time. Keep everything you listed working. Don't publish or deploy anything. I'll test it in the preview first. Then tell me exactly what you changed, file by file, and walk me through the checks from your answer so I can confirm everything still works. If there's a mobile app that's already released, remind me to test it after publishing.
body-parser vulnerable to denial of service when invalid limit value silently disables size enforcement
Fix: update to 1.20.6
🔧Not sure how to fix these? A Verilay Self Fix session walks you through each fix with your AI builder, checks its replies, and rescans to confirm. Coming soon. Get early access →
Scores may vary slightly between runs as findings are AI-generated. A meaningful improvement (e.g. C → B) after applying fixes indicates real progress.
AI disclaimer: Analysis is generated by Claude AI and may contain false positives or miss issues. Always verify findings with your AI builder before making changes. This is not a professional security audit. See full terms.