# 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. ## Key facts - 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. ## What it checks - Code analysis (SAST): Untrusted data is followed from where it enters to where it does damage, across functions and files, with models of the usual frameworks such as Spring, Django, Flask, Express, Laravel, Rails and ASP.NET. - Dependencies (SCA): Every package and lock file is matched against public vulnerability sources. You get the version that fixes each issue and which update removes the most risk. - Secrets: Hundreds of kinds of credentials: cloud, CI/CD, version control, package registries, messaging, payments, databases and private keys. Validated offline and always shown masked. - Infrastructure as code: Kubernetes, Helm, Dockerfile, Terraform and CloudFormation, normalised to what the cluster or the cloud will really apply. Covers AWS, GCP and Azure with CIS and NSA references. - Pull requests: Only what is new in each pull request, with a fingerprint that tolerates code being moved. Findings arrive as comments and as SARIF. - Your own rules: Write rules for your codebase with a syntax compatible with Semgrep. Suppress a finding with a reason, an owner and an expiry date. - Compliance mapping: Each finding mapped to CWE, OWASP Top 10, OWASP ASVS and PCI DSS. - Reports and exports: A plain-language explanation of every finding. Exports in SARIF for GitHub, GitLab and Azure DevOps, plus JSON, HTML and PDF. ## Coverage - Web and services: Python, JavaScript, TypeScript, Java, Kotlin, Scala, Groovy, Go, C#, VB.NET, PHP and Ruby. - Systems: C, C++ and Rust. - Scripts and others: Bash, PowerShell, Perl, Lua, Solidity, Elixir, Erlang, Apex and R. - What we catch: Injection (SQL, command, code, template, LDAP, XPath), XSS, SSRF, path traversal, open redirect, unsafe deserialization, weak cryptography, insecure cookies, unverified TLS and memory errors in C and C++. ## Pricing - No account: 1 scan a day, simple report (verdict and top fixes). - Deckhand (free account): 5 scans a day up to 30 a month, scan history, simple report. - Skipper ($19 a month, or $190 a year): 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. - Captain ($59 a month, or $590 a year): 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. - Fleet ($149 a month, or $1,490 a year): 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. - Charter (on demand): $29 per 100 scans with the full report, no subscription. - Yearly licences cost 10 months instead of 12. ## Trust - Security practices aligned with ISO/IEC 27001 (alignment, not certification). - GDPR compliant. - The repositories you send are deleted when the analysis ends. Only the report is kept. - A data processing agreement (GDPR Article 28) applies to every customer: https://scancodebase.com/dpa/ - Data is stored and processed on servers in the European Union. - The website sets no cookies and has no analytics. - Available in English and Spanish. Spanish pages are under /es/. - Sign in and accounts: https://platform.scancodebase.com/ - Deleted when the analysis ends: What you send is deleted as soon as the analysis finishes. We keep the report, not the content. - Nothing is run: We read what you send us. We do not start it, install it or import it. - Nothing goes to third parties: No binary, code or secret you send us is passed on to an outside service. Reference databases are queried locally. - Secrets stay masked: A secret we find is shown masked, never in clear, and is never tested against the provider it belongs to. - No AI in the verdict: Findings do not depend on a language model. Each one can be explained and repeated. - Same input, same result: The same content gives the same report on any machine and at any time, so a report can be reproduced for an audit. - Built for hostile content: Readers have limits and workers are isolated, so a malicious file cannot compromise the service. ## Not available yet - Cloud posture: Attack paths from the internet to your data across AWS, GCP and Azure, joined with your code and images. - AI security: Hidden instructions in prompts and risky agent and MCP configuration. - Mobile apps: Static analysis for mobile applications. - Self-hosted and air-gapped: The same product inside your own infrastructure, with no internet connection. ## Pages - [Home](https://scancodebase.com/): overview, example report and FAQ - [Features](https://scancodebase.com/features/): everything the scanner checks - [Pricing](https://scancodebase.com/pricing/): plans and comparison table - [Compliance](https://scancodebase.com/compliance/): GDPR, data in the EU, and how reports support CRA, NIS2, DORA, PCI DSS and ISO 27001 - [Security](https://scancodebase.com/security/): how data is handled - [Documentation: Overview](https://scancodebase.com/docs/): How to use scancodebase: scan from the browser, the sc command line, a git push, your CI pipeline or the API, and download the reports. - [Documentation: Command line](https://scancodebase.com/docs/cli/): Install the sc command line tool, scan a repository with one command, read the report in your terminal and download it as PDF, JSON or SARIF. - [Documentation: git push](https://scancodebase.com/docs/push/): Scan a repository with the tool you already have: add scancodebase as a git remote and push the branch. Nothing to install. - [Documentation: API](https://scancodebase.com/docs/api/): The scancodebase REST API: start a scan, check its status, list your reports and download them as JSON, PDF or SARIF. With curl examples. - [Documentation: CI pipeline](https://scancodebase.com/docs/ci/): Add scancodebase to GitHub Actions or GitLab CI: install the sc command line, scan every change and stop the pipeline on serious findings. - [Documentation: Reports](https://scancodebase.com/docs/reports/): What a scancodebase report contains, the difference between the simple and the full report, the formats you can download and how to delete a report. - [Status](https://scancodebase.com/status/): service status and regions (Spain primary, Germany secondary) - [Full text for AI assistants](https://scancodebase.com/llms-full.txt) - [Cookie policy](https://scancodebase.com/cookies/) ## Features in detail - [Code analysis (SAST)](https://scancodebase.com/features/sast/): scancodebase is a static analysis (SAST) tool that follows untrusted data through your code, across functions and files, and shows the full path of every finding with a proposed fix. - [Dependency scanning (SCA)](https://scancodebase.com/features/dependency-scanning/): scancodebase is a software composition analysis (SCA) tool: it reads your manifests and lock files, matches every package against public vulnerability sources and tells you which update matters most. - [Secret scanning](https://scancodebase.com/features/secret-scanning/): scancodebase scans your files and your git history for credentials and shows each one masked, with its type and location. - [Infrastructure as code](https://scancodebase.com/features/iac-scanning/): scancodebase checks Kubernetes, Helm, Terraform, CloudFormation and Dockerfiles after resolving variables, modules and templates, so it evaluates the configuration your cluster or cloud will actually get. - [Pull request scanning](https://scancodebase.com/features/pull-request-scanning/): scancodebase scans the changes in each pull request and reports only the findings that are new, so a review is never buried under old ones. - [Your own rules](https://scancodebase.com/features/custom-rules/): scancodebase lets you add rules for the patterns that matter in your own code, written with a syntax compatible with Semgrep. - [Glossary](https://scancodebase.com/glossary/): plain definitions of the terms used in reports ## Guides - [SAST vs SCA: what is the difference?](https://scancodebase.com/guides/sast-vs-sca/): What each one finds, what it misses and why you need both. - [How to find secrets in a git repository](https://scancodebase.com/guides/find-secrets-in-git-repository/): Where keys hide, and what to do when you find one. - [Pre-merge security checklist](https://scancodebase.com/guides/pre-merge-security-checklist/): Eight checks to run on a pull request before you merge it. - [What is SQL injection, and how do you fix it?](https://scancodebase.com/guides/what-is-sql-injection/): How it works, how to spot it and the fix that always applies. - [How to prioritise dependency vulnerabilities](https://scancodebase.com/guides/prioritise-dependency-vulnerabilities/): From hundreds of alerts to a short list you can finish. ## Related - [scancontainer](https://scancontainer.com/): scancontainer is an online scanner for Docker and OCI container images. It reads every file in every layer without running the image and reports vulnerabilities, malware, tampered files, leaked secrets, configuration problems and licences, with the proof for each finding.