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.
scancodebase follows untrusted data through your code, checks what your code depends on and reads your configuration. Here is what that covers.
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.
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.
Hundreds of kinds of credentials: cloud, CI/CD, version control, package registries, messaging, payments, databases and private keys. Validated offline and always shown masked.
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.
Only what is new in each pull request, with a fingerprint that tolerates code being moved. Findings arrive as comments and as SARIF.
Write rules for your codebase with a syntax compatible with Semgrep. Suppress a finding with a reason, an owner and an expiry date.
Each finding mapped to CWE, OWASP Top 10, OWASP ASVS and PCI DSS.
A plain-language explanation of every finding. Exports in SARIF for GitHub, GitLab and Azure DevOps, plus JSON, HTML and PDF.
In detail
Coverage
What makes it different
You see where the untrusted data comes in and every step it takes to the risky call, across functions and files.
Each finding comes with a safer way to write that line, for its language and its kind of flaw.
Findings are ranked by whether they can be reached from an entry point, so the report starts with what matters.
On a pull request we report what is new, even if the code has moved, so old findings do not bury the new ones.
A key we find is shown masked and is checked offline. It is never tested against the provider it belongs to.
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.
On the way
Coming soon
Attack paths from the internet to your data across AWS, GCP and Azure, joined with your code and images.
Coming soon
Hidden instructions in prompts and risky agent and MCP configuration.
Coming soon
Static analysis for mobile applications.
Coming soon
The same product inside your own infrastructure, with no internet connection.
Same team, same short reports
scancontainer checks the image you build from this code: vulnerabilities, malware, tampered files and secrets.