Is johnbillion/query-monitor 4.1 vulnerable?
Composer · 2 releases from 4.1.0 to 4.1.1 · latest johnbillion/query-monitor is 4.1.1 · checked 18 Nov 2026
No known advisories in the last release
No. No johnbillion/query-monitor 4.1.x release has a known security advisory.
Is your project on an affected johnbillion/query-monitor?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Which of your client projects are still on johnbillion/query-monitor 4.1?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact johnbillion/query-monitor version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other johnbillion/query-monitor versions
- johnbillion/query-monitor 4.0
- johnbillion/query-monitor 3.20
- johnbillion/query-monitor 3.19
- johnbillion/query-monitor 3.18
- johnbillion/query-monitor 3.17
- johnbillion/query-monitor 3.16
- johnbillion/query-monitor 3.15
- johnbillion/query-monitor 2.17
- johnbillion/query-monitor 2.16
- johnbillion/query-monitor 2.15
- johnbillion/query-monitor 2.14
- johnbillion/query-monitor 2.13
- All johnbillion/query-monitor advisories
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Composer registry. Refreshed daily.