Canonical: https://instain.ru/en/ai/sourcery/
Language: en

Sourcery  service

# Sourcery. 

AI Review of Changes and Repository Security Check

4.48 / 5    [Directory score](https://instain.ru/en/ai/sourcery/#editorial-rating) [Official website ](https://www.sourcery.ai/)

Sourcery adds an automatic revision to the development process: a summary of changes, comments on lines and suggestions for corrections. Individual functions check the safety of repositories.

![Sourcery: documentation on code review and security checks](https://instain.ru/assets/images/sourcery-screen-0b9adeaa5b01-1200.webp)

Official Sourcery documentation: documentation on code review and security checks.  [Open the source ](https://docs.sourcery.ai/)

## One more pass before the merger

Sourcery integrates AI review into pull-request workflows. It prepares change summaries, comments on specific lines and suggested fixes. This directs attention to possible logic errors, overlooked cases or security issues. Assessing the quality of a change remains part of the team’s development process.

The product works with GitHub and GitLab, and the documentation separately covers corporate servers. IDE integrations are provided for checking in the editor. Such a set allows you to receive comments at different stages, but the same product name does not mean the same access to all functions.

## Verifiable observation

A useful comment should explain what input is causing the problem and how the behavior of the program is changing. For example, when changing the date parsing function, it is worth checking the empty string, the wrong format and the month border. If the service offers an edit, compare it to the expected contract function.

Not every confident remark is a defect. Sometimes the necessary verification is already performed in another layer, and the proposed change creates duplication. Ask for context, reproduce an example and only then apply the correction. The pull request summary makes it easier to read, but does not replace the diff itself.

## A separate security workflow

Documentation Sourcery describes checks on secrets, code, infrastructure configurations, dependencies, and licenses. The results have their own review process, severity and access rules. Through API, you can transfer security findings to other tools; this should not be confused with universal API code generation.

The scanning functions and the depth of the available results depend on the plan. Before the pilot, it is useful to choose a small group of repositories and determine who is analyzing the problems found. Otherwise, additional messages can increase the queue without improving the speed of corrections.

## Limits affect the workflow

Sourcery takes into account the volume of code changed and the rolling budget of use. Too much diff or an exhausted quota can cause a revision to be missed. Therefore, the absence of comments can not be considered a proof of the absence of errors: first check whether the check itself is completed.

Public repositories are available for free Open Source. For private development, there are paid plans with a trial period. Own placement and additional corporate opportunities are discussed separately. Current restrictions should be checked before the whole team is connected.

## How to evaluate the result

Compare the problems found with real replicable cases and take into account the cost of false comments. It is not only the number of comments that matters, but also their usefulness for a particular project. For closed code, separately study the data processing of the selected placement option and the connected model. The presented scenario is a recommendation for verification, its own comparative quality test was not carried out here.

## Suitable tasks

- Get an initial pull-request review

- Dealing with Risky Changes Before Merging

- Check code in IDE

- Transfer security scanning results to your system

Features 

## Strengths

- Comments and proposed corrections next to diff

- GitHub, GitLab and corporate placement options

- Scan security and API results on the appropriate plan

Things to consider 

## Limitations

- Comments may be incorrect or incomplete

- Size diff and weekly budget limit checks

- Self-hosted and some security features are available on separate plans

## Selection and conditions

Free access

Yes

Trial period

Yes

No sign-up required

Not confirmed

Russian interface

Not confirmed

Local installation

Yes

API

Yes

“Not confirmed” means there is not enough information. The feature may still be available; check the developer’s terms.

Input formats

Code, Text

Result

Code, Text

### Terms

A free Open Source plan is available for public repositories. Paid plans are billed per seat and include a trial; review limits account for diff size. Connection to GitHub or GitLab, IDE extension; corporate servers and own placement have separate conditions.

From task to first result

## Practical example

Task

Get an initial pull-request review

What to prepare

A small change in the function of analyzing dates and a description of its expected behavior.

### Task brief or prompt

Review the function change for an empty string, an invalid format and a month boundary. For each genuine bug, identify the line, a reproducible input and the expected result. Do not change the public interface unnecessarily.

### Expected result

Comments on specific lines and suggestions for limited corrections.

### How to check the result

- Repeat each comment with a separate example.

- Check the diff and run the change-related tests.

An editorial teaching example of a task brief, not the result of hands-on testing of the service. Check that the required mode is available, that you have rights to the source material and that the intended use of the result is permitted.

Check details

## Official sources

-  [Sourcery: code review ](https://www.sourcery.ai/)

-  [Review, scanners and API ](https://docs.sourcery.ai/)

-  [Plans and limits ](https://docs.sourcery.ai/admin/plans/)

-  [Enterprise self-hosting ](https://docs.sourcery.ai/trust/self-hosted-sourcery/)

This description is based on the developer’s material. Features, prices and availability may change; check the primary source before use.

About the tool

Developer

Sourcery

Category

[Code](https://instain.ru/en/category/code/)

Access

Connection to GitHub or GitLab, IDE extension; corporate servers and own placement have separate conditions.

Payment

A free Open Source plan is available for public repositories. Paid plans are billed per seat and include a trial; review limits account for diff size.

API

Yes, from the developer

[Developer terms ](https://docs.sourcery.ai/admin/plans/)

Directory score

4.48 / 5 

Features

4.50 / 5 

Workflows

4.50 / 5 

Ecosystem

4.40 / 5 

Documentation

4.50 / 5 

Scores are an editorial guide to the directory. They are not user reviews or the results of personal testing.

[See the methodology ](https://instain.ru/en/methodology/)

Keep exploring

## For similar tasks

[Full category  ](https://instain.ru/en/category/code/)

Code 

###  [Zed AI](https://instain.ru/en/ai/zed-ai/)

Agents, edits and hints inside the Zed editor with a choice of models

4.58 / 5   editor  

Similar tasks; compare terms, formats and limitations

Code 

###  [Open Interpreter](https://instain.ru/en/ai/open-interpreter/)

Terminal agent with choice of provider, models and command execution control

4.43 / 5   Agent  

Similar tasks; compare terms, formats and limitations
