OpenTremor

Product tour · Tech lead

Your team's rules checked on every pull request, so reviews talk about the design.

See a pull request reviewed against your rules, a false positive dismissed once, the existing code scanned, and a goal tracked.

The product tour for your role: PDF·PowerPoint

Tech lead

Every pull request checked against your team's rules

As a tech lead, I want every pull request checked against our written standards, so reviewers stop repeating the same comments.

Your standards are in a wiki and in people's heads. A pull request follows them only if the reviewer knows them and has time.

What to notice

  • The rule is your team's own, written in plain words. You do not need a special rule language.
  • The finding explains the risk, not only the line of code.
  • The fix is a normal GitHub suggestion. OpenTremor never commits code for you.

Step 1 of 5

A developer opens a pull request.

The pull request adds a list of invoices. Its database query returns the invoices of all customers, not only the caller's.

Do it yourself: the step-by-step guide

Reviewer

Dismiss a false positive once

As a reviewer, I want to dismiss a false positive with a reason, so it does not come back after every push.

Most review tools forget. The same false positive comes back on the next commit, and people start to ignore the tool.

What to notice

  • The note stays with the finding, for the next reviewer and for audits.
  • Each decision counts against the rule. When reviewers often reject a rule, OpenTremor suggests a change to it.

Step 1 of 3

Every pull request is reviewed against your rules.

OpenTremor's comment on the pull request lists two findings: the customer data bug and a slow, blocking call in a script.

Do it yourself: the step-by-step guide

Platform engineer

Find problems already in your code

As a platform engineer, I want to check an existing repository against our standards, so I can find its problems before they cause an incident.

Pull request review sees only the changed code. Nobody checks the older code, so nobody knows how much of it breaks the rules.

What to notice

  • A scan never blocks a pull request. It only shows the current state of the code.
  • OpenTremor never sends the same code to the AI model twice.

Step 1 of 3

A platform engineer scans the code already on the default branch.

The repository's Scan tab shows what a scan will check. One click scans the main branch.

Do it yourself: the step-by-step guide

Engineering director

Track an engineering goal across pull requests

As an engineering director, I want to know if our changes move us toward our goals, not only if they fix single issues.

Goals like customer data isolation or a migration live in a slide deck. Nobody knows the real progress, and nobody sees when a pull request makes it worse.

What to notice

  • A measured step is done when its rules have no open findings left in the product.
  • One pull request never completes the goal by itself. A step is done when its count reaches zero, or when a person marks it as done.

Step 1 of 4

An engineering director sets a goal, with a step OpenTremor can measure.

The goal "Tenant isolation everywhere" has a step that OpenTremor measures: the number of open findings for one rule. A scan found one.

Do it yourself: the step-by-step guide

Try it on your own pull requests.

Connect a repository, write one rule, and open a pull request.

See all the stories