Best alternative to OSV-Scanner, meet Jikida.
OSV-Scanner is a great free tool that checks your dependencies and lockfiles against the OSV vulnerability database. It does not test your running website, block a live attack, or watch uptime, and you run it yourself. Jikida scans dependencies too, then adds a hosted pentest and live protection in one account.
Why teams pick Jikida over OSV-Scanner.
OSV-Scanner is an excellent, free dependency scanner from Google. It reads your lockfiles and manifests and checks each package against the OSV database, the same open vulnerability source many tools rely on, and it runs cleanly in CI. For confirming whether your dependencies carry known issues, it does its job well.
A dependency scan never tests the running application, though. OSV-Scanner does not tell you the deployed site is down, block an attack in progress, or check the live host for exposed files and weak headers, and there is no hosted dashboard. Jikida scans your dependencies against OSV too, then adds a pentest of the live app, a managed firewall and uptime monitoring.
People often ask whether Jikida replaces OSV-Scanner. Both check dependencies against OSV, but Jikida goes further with a hosted repo scan, a pentest of the deployed app, and live protection, from one account with a free tier.


Switching from OSV-Scanner to Jikida.
Keep running OSV-Scanner in CI to catch vulnerable dependencies before you ship, then let Jikida cover the rest. Jikida runs its own repo scan that checks dependencies against OSV and adds secret detection, then a pentest of the deployed app: headers, TLS, exposed .env and .git files, open ports, admin panels and reflected XSS, with a plain fix for each finding.
Because a dependency scanner never watches the live host, Jikida adds a managed firewall that blocks attacks and uptime monitoring for availability, SSL and domain expiry. The free tier needs no card, so you can run it beside OSV-Scanner with nothing to migrate.
Compare Jikida with the rest.
How to switch from OSV-Scanner without a monitoring gap.
Migrating off OSV-Scanner is a five-minute job, not a project. You keep OSV-Scanner live while you set Jikida up, move your sites and alerts across, switch on the WAF and pentest OSV-Scanner never offered, and only then cancel. Here is the exact order.
-
01
Keep OSV-Scanner running while you set up
No rip-and-replace. Create a free Jikida account and add your sites there first, and OSV-Scanner stays live the whole time, so there is never a monitoring gap during the move.
-
02
Add your sites and endpoints
Point Jikida at the same URLs, domains and API endpoints you watch in OSV-Scanner. Uptime checks, SSL and domain-expiry monitoring and a public status page turn on the moment a site is added: no agent to install, no DNS change.
-
03
Wire up the alerts you already use
Connect email, Slack, Discord, Telegram or a signed webhook, and install the Jikida Alerts phone app. The call-style Alarm level rings through silent mode and Do Not Disturb for the 3am outage you cannot sleep through, something OSV-Scanner cannot do.
-
04
Turn on the security OSV-Scanner does not have
This is the real upgrade: a managed WAF in one SDK line, a scheduled pentest that grades your site A–F, repo and secret scanning, and active deception, all in the same account, at no extra vendor. Monitoring and security stop being two bills.
-
05
Run both for a cycle, then cancel OSV-Scanner
Watch the two side by side for a billing cycle. Once you trust the Jikida alerts and grades, cancel OSV-Scanner and consolidate. Most teams find they were paying for uptime and still had no security layer at all.
Frequently asked questions.
Everything people ask before they switch from OSV-Scanner. Still unsure? We are one message away.
For teams that want more than dependency scanning, yes. OSV-Scanner is a free CLI that checks lockfiles against the OSV database. Jikida checks dependencies against OSV too, then adds secret scanning, a live-app pentest, a managed WAF and uptime, from one account with a free tier.
It does not have to. Keep OSV-Scanner in CI for dependency checks, and use Jikida for the hosted repo scan, live-app pentest, WAF and uptime that a dependency CLI does not cover. They complement each other.
It scans for secrets, tests the running app, and protects it. You get a hosted repo scan, a live-app pentest, a managed WAF that blocks attacks, uptime and SSL monitoring, and a fix per finding, alongside the OSV dependency check.
OSV-Scanner is free and open-source and you self-host it. Jikida is a hosted platform with a free tier that needs no card, covering one repo scan, one pentest, uptime and a basic firewall, then paid plans from $19 a month.
Use OSV-Scanner when you want a free CLI to check dependencies in your pipeline. Use Jikida when you want dependency checks plus secret scanning, a live-app pentest, a managed WAF and uptime in one account. Many teams run both.
One platform · One install
Pentest, scan and protect from one account.
A live-app pentest, repo and secret scanning, a managed firewall and monitoring — free to start, no card. Plans from $15/mo.