Skip to content
Security
Repository security

What needs attention in your code?

Assess repository code, review findings with their evidence, and prepare eligible fixes for your team's review.

Start a scanSee how a scan works
Controlled betaGetting started

A scan that could not examine enough of the repository is reported as limited coverage, never as an all-clear.

Illustrative product walkthrough
SecurityExample workspace

Scan result

acme / checkoutmain
Complete

Confirmed findings

2

Review candidates

2
Severity distributionHigh1Medium1

Confirmed findings

2
  • Unsanitized input in a query builderHigh
    api/orders/route.ts:42Confirmed
  • Unescaped input in a templateMedium
    components/SearchBar.tsx:67Confirmed

Review candidates

2
  • Missing authorization checkHigh· CANDIDATE
    app/webhooks/handler.ts:18Needs validation
  • Weak session expiry windowLow· CANDIDATE
    lib/auth/session.ts:23Unconfirmed
Export as JSON or CSVJSON · CSV
The pipeline

From repository to review.

  1. Select a repository

    Review the repositories accessible through each source connection, add the ones you need, and check whether each is currently eligible to scan.

    Illustrative product walkthroughacme / checkout / mainExample workspace
    • acme / checkout
    • acme / payments
    • acme / web

  2. Scan a branch

    Start a scan on the branch you want to assess and follow its progress in the console.

    Illustrative product walkthroughacme / checkout / mainExample workspace
    • Queued
    • Preparing repository
    • Analyzing code
    • Preparing report

  3. Review the findings

    Each finding carries a severity and a separate proof state saying how well evidenced it is, and names the file and line where the location is known.

    Illustrative product walkthroughacme / checkout / mainExample workspace

    • Unsanitized input in a query builder

      api/orders/route.ts:42

      HighConfirmed

    • Missing authorization check

      app/webhooks/handler.ts:18

      HighNeeds validation

  4. Review an eligible fix

    For a confirmed dependency finding in a connected GitHub repository, Relane can prepare a deterministic patch for review. It opens a pull request only after explicit approval; a merge triggers a post-merge rescan.

    Illustrative product walkthroughacme / checkout / mainExample workspace

    GitHubpackage.json

    • Review the proposed diff
    • Approve before any pull request
    • Check post-merge verification
Working with a scan

Follow progress. Share the result.

Follow scan progress

A scan reports its progress through ordered phases, keeps running if you close the page, and can be cancelled while it runs.

Export a result

Any result can be exported as JSON or CSV from the console, and the export carries the same coverage verdict the screen showed.

Configure repeat assessments

Configure repository schedules and policies, and send selected scan events to email, Slack, Teams or an HTTPS webhook. Review actual execution and delivery outcomes in the console.

Team workflows

Investigation, remediation and handoff.

Integrations

Connect your source repositories.

Connect GitHub, GitLab Cloud or Bitbucket Cloud, authorize source access, and add the repositories you want to assess to your workspace.

GitHub

GitHub connection guide

GitLab Cloud

GitLab Cloud connection guide

Bitbucket Cloud

Bitbucket Cloud connection guide
Evidence over volume

Separate findings from review candidates.

Proof state distinguishes confirmed findings from items that need validation or remain unconfirmed. Severity is reported separately.

Read coverage limits

The console distinguishes findings, clean results, limited coverage, cancelled scans and runs that produced no result.

Findings
Clean result
Completed with limited coverage
Cancelled
No result produced
Access and evidence

Access, approval and assessment limits.

Workspace roles

Repositories, scans, findings and notification destinations belong to a personal or organization workspace, with owner, admin and member roles.

Approval to publish

For a confirmed dependency finding in a connected GitHub repository

It opens a pull request only after explicit approval; a merge triggers a post-merge rescan.

Assessment limits

A scan is presented as clean only when coverage was adequate and nothing was found.

Get in touch

Discuss access and assessment scope.

Security & product inquiries
security@relane.ai

Security and product enquiries reach the team at security@relane.ai.

Prepare an email

Enter your name, email and message. Review and send the draft in your mail client.

Enter your name.

Enter your email address.

Enter a message.

Open in your mail client

Do not include source code, credentials or other sensitive material in this message.

Start with one repository.

Controlled beta access. Plans, pricing, supported capabilities and availability are confirmed in writing during approved onboarding. Self-service plan selection and checkout are not currently available.

Read the documentationGet in touch