Code security and dependency scanner Scan it before you merge it.

scancodebase checks your code for security flaws, your dependencies for known vulnerabilities and your files for leaked secrets, then tells you what to fix first.

1 free scan a dayNo account. No card.

Other ways: Private repository Upload a file Terminal

Connect your code

Choose where your repository lives. You sign in there, pick the repositories to share and come back to scan.

Read-only access. You can remove it at any time.

Works with

What makes it different

Why scancodebase is different

A trace for every finding

You see where the untrusted data comes in and every step it takes to the risky call, across functions and files.

A proposed fix, not just a warning

Each finding comes with a safer way to write that line, for its language and its kind of flaw.

Priorities, not endless lists

Findings are ranked by whether they can be reached from an entry point, so the report starts with what matters.

Only what changed

On a pull request we report what is new, even if the code has moved, so old findings do not bury the new ones.

Secrets never leave

A key we find is shown masked and is checked offline. It is never tested against the provider it belongs to.

Nothing goes to third parties

Your code is not sent to an outside service. Results do not depend on an AI model, so the same code always gives the same report.

Who it is for

One scan, a different answer for each team

Developers

Find the flaw while the code is still open in your editor, with a fix next to it.

Application security

A trace for every finding, your own rules and suppressions with an owner and an expiry date.

Team leads

Only new findings on each pull request, so reviews stay short.

Compliance

Findings mapped to OWASP, CWE and PCI DSS, and a record of what was fixed and when.

What we check

What scancodebase checks in your repository

Security flaws in your code

SQL, command and template injection, XSS, SSRF, path traversal, unsafe deserialization and weak cryptography, each with the file, the line and the trace.

Vulnerable dependencies

Every package your code brings in, matched against known vulnerabilities, with the version that fixes each one.

Secrets

API keys, tokens, private keys and passwords in your files and in your git history.

Infrastructure as code

Kubernetes manifests, Helm charts, Dockerfiles, Terraform and CloudFormation, evaluated as they will really be applied.

Licences

The licence of each dependency, so nothing incompatible with your policy slips in.

What to fix first

Findings grouped by root cause and ranked, so one fix can close several at once.

See every feature

How it works

How to scan a repository

  1. 01

    Send us the repo

    Paste its URL, upload a .zip, or push it like you would to any git remote.

  2. 02

    We read every file

    Your code, your dependencies and your configuration. Nothing is executed.

  3. 03

    You fix what matters

    A short list in order of importance, each item with its trace and the fix.

The report

A scan report you actually finish reading.

Most scan reports are a wall of codes. Ours starts with what to fix today, why, and the fix. The rest is counted and parked.

src/api/users.jsExample report

Almost ready. Fix 3 things first.

  1. 1. Fix the query in users.js

    Line 43 builds a SQL query by joining strings with user input. Pass the value as a parameter instead.

    db.query('SELECT * FROM users WHERE id = ?', [id])
  2. 2. Take the key out of users.js

    Line 41 has it written in the code, so it is in every copy of the repo. Read it from the environment, then rotate the key.

    const KEY = process.env.API_KEY
  3. 3. Update lodash

    Line 40 imports a version with known vulnerabilities. The current release fixes them.

    npm install lodash@latest

31 low-risk notes can wait.

Free gets you the simple report. Paid gets you the full one.

Free: no account and Deckhand

Simple report

Enough to know where you stand.

  • The verdict: ready, almost ready or not ready
  • How many findings there are, by severity
  • The top fixes, each with its file and line
  • Which dependencies have known vulnerabilities

Paid: Skipper, Captain and Fleet

Full report

Everything you need to fix it and to prove it.

  • Every finding with its step-by-step trace
  • A proposed fix for each one
  • Whether each finding can be reached from an entry point
  • Dependencies, secrets, infrastructure as code and licences
  • Findings grouped by root cause
  • Exports: SARIF for GitHub, GitLab and Azure DevOps, HTML and PDF

Security and compliance

Careful with your code. Serious about your data.

1M+

Docker images scanned on scancontainer, our sister product.

ISO 27001

Our security practices are aligned with the standard, from how we build to how we run the service.

GDPR

We comply with European data protection regulation in how we handle your account and your code.

Data in the EU

Your repositories and reports are stored and processed on servers in the European Union.

See how we comply, and how our reports help you with the CRA, NIS2, DORA and PCI DSS

Pricing

Free to start. Fair when you grow.

Free scans come with the simple report. Paid plans give you the full report and a monthly pool of scans.

No account? You still get 1 scan a day, with the simple report. Scan without signing up

Billing

Deckhand

$0 free account

Free for ever

For your own projects.

  • 5 scans a day, up to 30 a month
  • Scan history
  • Simple report: verdict and top fixes
Create free account

Skipper

$19 a month

$190 a year

or $190 a year

2 months free

For one developer who ships most weeks.

  • 100 scans a month
  • 1 seat
  • Full report with trace and fix
  • Dependencies, secrets and IaC
  • SARIF export
  • Scan from your CI pipeline

Extra scans: $19 per 100.

Choose SkipperChoose Skipper

Captain

$59 a month

$590 a year

or $590 a year

2 months free

For a small team.

  • 600 scans a month, shared
  • 5 seats
  • Everything in Skipper
  • Pull request scans: only what changed
  • Your own rules
  • OWASP, CWE and PCI DSS mapping
  • Licence checks

Extra scans: $10 per 100. Extra seats: $10 each a month.

Choose CaptainChoose Captain

Fleet

$149 a month

$1,490 a year

or $1,490 a year

2 months free

For the whole engineering team.

  • 2,000 scans a month, shared
  • 15 seats
  • Everything in Captain
  • Metrics by repository and team
  • Alerts when a new CVE hits your code
  • API access

Extra scans: $8 per 100. Extra seats: $8 each a month.

Choose FleetChoose Fleet

On demand

Charter: $29 per 100 scans

No subscription needed. Buy a pack of 100 scans with the full report and use them at your own pace.

Buy a pack

Choosing a plan takes you to the platform: you create your account, pay there and start scanning. You can change plan later from your account.

Compare all plans

FAQ

Questions people ask before their first scan

What is scancodebase?

scancodebase is an online security scanner for source code. It combines static analysis (SAST), dependency scanning (SCA), secret detection and infrastructure-as-code checks, and reports each finding with a step-by-step trace and a proposed fix.

Is scancodebase free?

Yes. You get 1 scan a day without an account and 5 scans a day, up to 30 a month, with a free account, which also keeps your scan history. Free scans come with the simple report: the verdict and the top fixes.

What is the difference between the simple report and the full report?

The simple report gives you the verdict, the number of findings and the top fixes. The full report, on paid plans, shows every finding with its step-by-step trace and a proposed fix, and adds dependencies, secrets, infrastructure as code and the exports.

Is this a SAST tool or an SCA tool?

Both. The code checks are static analysis (SAST) and the dependency checks are software composition analysis (SCA), in one report.

Do you keep my code after the scan?

No. Your repository is deleted when the analysis ends. Only the report is kept.

Does my code go to anyone else?

No. No code or secret you send us is passed on to third parties. The reference databases are queried locally.

Do you use AI to decide what is a finding?

No. The verdict does not depend on a language model. Results are deterministic and each one comes with its trace.

Do you test the secrets you find?

No. Secrets are validated offline, by their structure, checksum and expiry, and against public lists of compromised keys. They are never tried against the provider.

Which languages do you scan?

Python, JavaScript, TypeScript, Java, Kotlin, Go, C#, PHP, Ruby, C, C++ and Rust, among others. The Features page has the full list.

How do I scan a repository?

Paste the repository URL in the box at the top of this page, or add scancodebase as a git remote and push. The documentation has the two commands.

Do you also scan Docker images?

Yes. scancontainer.com is our scanner for Docker images, with the same short reports.

Same team, same short reports

Scan your Docker images too

scancontainer checks the image you build from this code: vulnerabilities, malware, tampered files and secrets.

Go to scancontainer

Scan yours before the next merge.