Repository scanning

Scan repositories with a remediation workflow attached.

Kagliostro helps teams analyze repositories, prioritize issues, and verify fixes after changes land.

Repository Security Scanning for Modern Engineering Teams

Scan repositories with Kagliostro to rank findings, inspect evidence, and route the important ones into remediation.

Why teams use it

  • Move from raw findings to prioritized remediation.
  • Scan connected private or public repositories.
  • Re-run scans after a fix to verify the outcome.

Typical examples

A production API repository before release.
A payment service after a dependency upgrade.

Concrete workflow

  1. Connect GitHub and pick a repository.
  2. Launch a repo scan with the right mode.
  3. Inspect evidence, fix, then re-scan.

FAQ

Can I scan private repositories?

Yes, once GitHub is connected in the workspace.

Can I rescan after a fix?

Yes. Re-verification is part of the intended workflow.

Do deeper modes use more credits?

Yes. Billing keeps that consumption visible.

Run a repository scan

Choose a repository, select the right depth, and focus on the findings that matter.

Create an account

Related pages