OpenTremor

Packs

Your code, infrastructure and pipelines, reviewed against your rules.

Each pack reads one kind of change and ships its own rules. Turn on the packs your products need, then add your own rules on top.

Each pack reads one kind of change and ships its own rules.

  • 13 official packs
  • 262 built-in rules
  • 5 scopes
OpenTremor checkpython-code-change
@@ routers/invoices.py @@ @router.get("/invoices")-def list_invoices(user: User = Depends(current_user)):- return repo.find(org_id=user.org_id)+def list_invoices(org_id: str, user: User = Depends(current_user)):+ return repo.find(org_id=org_id)
CRITICALPYCC-001

Tenant ID taken from the query string instead of the authenticated user

Coverage

What OpenTremor reviews today.

Each pack runs its built-in rules and your custom rules. Self-hosted: every pack, unlimited. Cloud: the packs share the 100 free analyses, then need a paid plan.

Code

Git diffs of .py files

Invariants a linter can't express: tenant scoping, missing auth guards, blocking calls in async paths

  • Python
  • Django
CRITICALTenant ID taken from the query string instead of the authenticated user
Show the diff
@@ routers/invoices.py @@ @router.get("/invoices")-def list_invoices(user: User = Depends(current_user)):- return repo.find(org_id=user.org_id)+def list_invoices(org_id: str, user: User = Depends(current_user)):+ return repo.find(org_id=org_id)

Git diffs of TypeScript and JavaScript files

Invariants a linter can't express: missing auth checks, injection, secrets exposed to the client

  • Node
  • Next.js
HIGHLive Stripe secret key committed in plain text
Show the diff
@@ src/lib/stripe.ts @@-const stripe = new Stripe(process.env.STRIPE_SECRET_KEY!);+const stripe = new Stripe("sk_live_51Hx…REDACTED");

Infrastructure

Output of terraform plan, including multi-stack Terramate runs

Each resource's planned end state, deduplicated by content hash

  • AWS
  • Any provider
  • Terramate
CRITICALPostgreSQL port 5432 open to the internet on db_ingress
Show the diff
# aws_security_group_rule.db_ingress will be created + resource "aws_security_group_rule" "db_ingress" { + type = "ingress" + from_port = 5432 + to_port = 5432 + cidr_blocks = ["0.0.0.0/0"] }

Git diffs of .tf files

What actually changed, block by block: approved modules, tags, security regressions

MEDIUMModule network no longer pins a version
Show the diff
@@ modules.tf @@ module "network" {- source = "terraform-aws-modules/vpc/aws"- version = "5.8.1"+ source = "terraform-aws-modules/vpc/aws" }
kubernetes31 rules

Git diffs of Kubernetes manifests and Kustomize files

Pod Security restricted profile, RBAC, exposure and Secrets, one object at a time

  • Manifests
  • Kustomize
HIGHContainer agent runs privileged
Show the diff
@@ deploy/agent.yaml @@ spec: containers: - name: agent securityContext:+ privileged: true
helm11 rules

Git diffs of Helm charts: values, templates and Chart.yaml

Risky values defaults, wildcard RBAC in templates, open dependency ranges, without rendering

HIGHChart Role grants every verb on every resource
Show the diff
@@ templates/role.yaml @@ rules:- - apiGroups: [""]- resources: ["configmaps"]- verbs: ["get"]+ - apiGroups: ["*"]+ resources: ["*"]+ verbs: ["*"]
ansible24 rules

Git diffs of Ansible playbooks, roles and variables

Each task: privilege escalation, secrets, hardening, performance and reliability

  • Debian
  • RHEL
  • Any distribution
HIGHShell task runs apt-get install where the apt module does the job
Show the diff
@@ roles/app/tasks/main.yml @@ - name: Install the app package- ansible.builtin.apt:- name: "{{ app_package }}"+ ansible.builtin.shell: apt-get install -y {{ app_package }}

CI/CD

Git diffs of GitHub Actions workflows and actions

Untrusted triggers that run PR code, script injection, unpinned actions, broad permissions

HIGHIssue title reaches a run: script, which allows shell injection
Show the diff
@@ .github/workflows/greet.yml @@ on: issues jobs: greet: steps:+ - run: echo "Thanks for ${{ github.event.issue.title }}"
gitlab-ci21 rules

Git diffs of .gitlab-ci.yml and included pipeline files

Remote includes, mutable images, Docker-in-Docker, unprotected deploys, secrets in logs and artifacts

HIGHPipeline includes CI config from a remote URL outside the instance
Show the diff
@@ .gitlab-ci.yml @@ include:- - project: platform/ci-templates- ref: v3.2.0+ - remote: https://example.com/ci/build.yml

Containers

dockerfile18 rules

Dockerfiles and their git diffs

Unpinned base images, unchecked downloads, secrets in layers, a final stage running as root

HIGHInstall script piped to sh with no checksum
Show the diff
@@ Dockerfile @@ FROM debian:12-slim-COPY install.sh /tmp/install.sh+RUN curl -fsSL https://get.example.com/install.sh | sh

Git diffs of Docker Compose files

Privileged services, Docker socket mounts, host namespaces, exposed database ports, literal secrets

CRITICALDocker socket mounted into watchtower gives it root on the host
Show the diff
@@ compose.yaml @@ watchtower: image: containrrr/watchtower+ volumes:+ - /var/run/docker.sock:/var/run/docker.sock

Dependencies

Git diffs of package.json, npm, Yarn and pnpm lockfiles, and .npmrc

New packages, lifecycle scripts, sources outside the registry, loosened ranges, a weakened .npmrc

  • npm
  • Yarn
  • pnpm
HIGHleft-pad now comes from a Git branch, not the registry
Show the diff
@@ package.json @@ "dependencies": {- "left-pad": "1.3.0"+ "left-pad": "github:someone/left-pad#main" }
Agent-manipulation detectionRuns on every change, whichever pack takes it, on every plan.
Anything else: genericA file no pack claims is still checked for secrets, destructive operations, open access and unsafe calls. Confidence is capped at medium.
Off until you turn them onA new organization reviews nothing until an admin enables its packs in Rules → Packs.

Not covered yet?

Tell us which format you need next.

No official pack reads these yet. Requests decide which pack we build next.

Request a pack
  • Go
  • Java
  • SQL migrations
  • CloudFormation
  • Jenkins
  • Azure Pipelines

Build your own

Our packs use the same public interface as yours.

The interface we useThe official packs are ordinary packages built on the same documented BasePack, with nothing held back.
No fork, no approvalImplement ingest() and get_rules(), declare one entry point, and pip install it.
Private or sharedKeep it internal for a proprietary file format, or publish it for anyone to install.
pyproject.tomlthe whole registration
[project.entry-points."opentremor_core.packs"]
my-pack = "my_pack:MyPack"

Declare one entry point and pip install the package. Core finds and registers it at startup, with no changes to OpenTremor itself.

Read the full guide

Rather have us build it?

We can build a custom pack for your internal file format or conventions as a scoped Services engagement, so you don't write or maintain the parser yourself.