Repository analysis

Analyze the code.
Inspect the evidence.

ComplyGuard runs deterministic source analysis against a real repository, profiles its engineering surface, correlates repeated framework signals into root risks and traces every finding back to its source location.

Control mappings identify engineering signals associated with GDPR, SOC 2 and ISO 27001. They are not legal conclusions, audit opinions or compliance certification.

Hosted scanner scope
RepositoryPublic GitHub
SourceTS · TSX · JS · JSX
Hosted archiveUp to 25 MB

The 25 MB limit applies to the downloaded GitHub repository archive used by the hosted scanner.

Analysis flow
GitHub repository→repository profile→AST analysis→root risk correlation→control mapping
Supported source

TypeScript, TSX, JavaScript and JSX files are analyzed by the current scanner.

Temporary processing

The GitHub archive is downloaded into temporary storage, analyzed and cleaned up after the request completes.

25 MB

Hosted scans accept GitHub repository archives up to 25 MB. This protects the hosted service from unexpectedly large downloads, extraction and AST workloads. Larger repositories can use the same deterministic scanner locally with pnpm scan ./path/to/project.

Rule packs

Choose which engineering control rule packs should execute. Selecting a framework does not mean ComplyGuard is performing a legal compliance audit.

GDPRPrivacy and personal data related engineering signals.
SOC 2Security, access, logging and operational control signals.
ISO 27001Information security engineering signals mapped to relevant controls.
01
Repository profile

Detected technologies and engineering risk surfaces provide context around the scan.

02
Root risks

Repeated framework signals are correlated into the underlying engineering problem where possible.

03
Source evidence

Every deterministic finding keeps its rule, framework, file, source location, evidence and remediation.