Compliance for source code Compliance, on both sides.

Two things matter: how we treat your data, and how our reports help you meet the rules that apply to you. This page covers both.

How we comply

What we commit to

GDPR

We comply with the EU General Data Protection Regulation, Regulation (EU) 2016/679. You can ask for access to your personal data, and for it to be corrected or deleted.

Data stays in the EU

Your repositories and your reports are stored and processed on servers in the European Union: Spain is the primary region and Germany the secondary one.

ISO/IEC 27001

Our security practices are aligned with the standard. That is alignment with its controls, not a certification.

No cookies, no trackers

This website sets no cookies and runs no analytics or advertising trackers, so there is nothing to consent to.

Deleted after the scan

The repositories you send are deleted when the analysis ends. Only the report is kept.

Data processing agreement

A DPA under Article 28 of the GDPR is published on this website and applies to every customer.

How the scanner treats what you send

How we help you comply

Rules and standards our reports support

Rule or standardWhat it asks forWhat you get from scancodebase
OWASP Top 10 and OWASP ASVSApplication security referencesThe reference lists most teams and auditors use for web application risks.Each finding mapped to its OWASP category.
CWECommon Weakness EnumerationThe shared catalogue of kinds of software weakness.Each finding carries its CWE identifier.
PCI DSSRequirement 6Bespoke and custom software must be developed securely and its vulnerabilities identified.Code findings mapped to PCI DSS, plus the known vulnerabilities in your dependencies.
EU Cyber Resilience Act (CRA)Regulation (EU) 2024/2847Products with digital elements must be developed securely, ship without known exploitable vulnerabilities and document their components.Static analysis of your own code, known vulnerabilities in your dependencies and the list of what you depend on.
NIS2Directive (EU) 2022/2555Article 21 asks for security in the development and maintenance of systems, including vulnerability handling.A security check on every change, with a record of what was found and when it was fixed.
ISO/IEC 27001Annex A, controls 8.28 and 8.29Secure coding principles must be applied and security tested during development.Scan results per repository as evidence that the control operates.
DORARegulation (EU) 2022/2554Financial entities must manage ICT risk across the software they build and run.Reproducible reports for your ICT risk file.
SOC 2Trust services criteriaAuditors look for evidence that vulnerabilities are found and dealt with.Dated, reproducible reports and a history of when each finding appeared and when it was fixed.
NIST SSDFNIST SP 800-218Software producers should review and analyse their code to find vulnerabilities, and respond to them.Static analysis on every change and a record of the vulnerabilities found and fixed.

A scan report is evidence, not a certificate. This page is a summary and not legal advice.

FAQ

Compliance questions

Does scancodebase make me compliant?

No tool does that by itself. A scan report is evidence that you look for problems and fix them. Compliance also depends on your own processes and, for some standards, on an audit.

Where does scancodebase keep my data?

Your repositories and reports are stored and processed on servers in the European Union. Spain is the primary region and Germany the secondary one.

Is scancodebase certified for ISO 27001?

Our security practices are aligned with ISO/IEC 27001. We state alignment, not certification.

Is the service GDPR compliant?

Yes. We comply with the GDPR, we do not sell personal data and we do not pass what you send us to third parties.

Scan yours before the next merge.