Skip to content
DashboardWebsite
opentremor-core — 1 open CRITICAL/HIGH finding

Standards review · commit a1b2c3d

CRITICALInvoice export scoped by an org_id from the query stringbilling/api/invoices.py:export_invoices

HIGHDatabase password committed in settings.pybilling/settings.py

Technical docs

Define your engineering standards once and apply them to every product — its repositories, its pull and merge requests, and the code already on the default branch. Connect GitHub, GitLab or any CI, bring your own model, and keep the decision with your team.

Install OpenTremor, configure it, connect it to your code hosts and models, and automate it over REST and MCP. To use the dashboard day to day, see the user guide.

  1. Connect

    Install the GitHub App, connect a self-managed GitLab group, or call the API from any CI job. Group your repositories into products.

  2. Review

    Each pull request and the code already on the default branch go to the pack that reads them. Your LLM checks them against your rules.

  3. Decide

    One report comment, a commit status that holds the merge, and triage that releases it. Each product page shows what is still open.

Standards

  • Rules in MarkdownEach rule is a paragraph. Apply it to the whole org, or to a team, product or repository.
  • Rules from ADRsRules drafted from your ADRs wait for a person on the To review tab.
  • Rule healthReviewer verdicts measure each rule and propose changes.
  • Thirteen packsPython and TypeScript code, npm, CI pipelines, Docker, Terraform, Kubernetes, Helm, Ansible, and a generic pack for everything else.
  • Agent-injection detectionFlags text that tries to steer an AI reviewer. The default checks use no LLM.

Products

  • Product viewEach product lists its repositories, changesets and open findings, with a report for the product or any of its repositories.
  • Repository scanReview the code already on the default branch, not only new changes.
  • Team routingRepositories belong to teams; reviews and alerts follow.
  • RevisionsEvery push is a revision. A fixed finding leaves the report on its own.
  • JiraOne Jira issue per finding, filed by team or product and kept in step with its status.

Integrations

  • GitHub AppYour organization registers its own App from the dashboard.
  • GitLabSelf-managed GitLab: one note per merge request and a merge check.
  • Merge gate from any CIGitLab CI, Bitbucket or anything else: fail the job when findings block.
  • Code suggestionsFixes posted as suggestions on the pull request, above a severity you choose.
  • AgentsAn agent runs analyses and manages OpenTremor as you, through MCP.

Platform

  • Your own LLMAnthropic, OpenAI, Mistral, or a self-hosted OpenAI-compatible endpoint.
  • Single sign-onOIDC and SAML SSO, SCIM provisioning, Google and Microsoft sign-in.
  • Roles and permissionsBuilt-in and custom roles; API keys narrowed by scope.
  • NotificationsSlack, Microsoft Teams, email and signed webhooks, per event and per team.
  • Self-hostedDocker Compose on one VM, or the Helm chart on Kubernetes.