SAFIYA Platform

Application Security Assessment, before it reaches production

Point SAFIYA at a GitLab repository and get findings back from eight parallel security agents — the kind of issues that usually only surface days before go-live in an external pentest, caught early instead.

How it works

Step 1
Connect a repo
Paste a GitLab URL, pick a branch/commit, and choose an assessment profile.
Step 2
Agents scan in parallel
Eight security agents run together against an ephemeral, auto-cleaned checkout.
Step 3
Findings get normalized
Results map to OWASP categories and dedupe by file:line — no duplicate noise.
Step 4
Review and export
Triage on the dashboard, assign owners, and export PDF/JSON/CSV reports.

Eight agents, running together

Each agent focuses on one category of risk, so a scan covers far more ground than a single generic linter pass.

Code

Injection, insecure deserialization, broken access control logic, unsafe eval, weak crypto.

Dependency

Reviews declared dependency manifests for known-vulnerable or suspicious versions.

Secrets

Hardcoded credentials, API keys, private keys, and tokens committed to the repository.

API

Broken object-level authorization, mass assignment, missing rate limits, verb tampering.

Auth

JWT handling, session management, password hashing, MFA/reset flows.

Infra

Dockerfile, docker-compose, nginx, and CI/CD pipeline configuration.

Frontend

XSS, CSP, cookie flags, CORS misconfiguration, client-side secret leakage.

Pentest

Race conditions, TOCTOU, file upload abuse, workflow bypass — read-only reasoning.

Ready to scan your first repo?