Open source policy that keeps up with people and coding agents.
For OSPO leads. One policy, written once and checked on every change, with a heads-up only when something needs your decision.
Written once, applied wherever code changes
Developers and their coding agents need the same rules, at the same moments.
You write a policy once and attach it to the projects it covers. Earnie puts it in the coding agent’s instructions, checks the agent’s changes when it finishes each turn, and checks every change at pre-commit and at merge.
How Earnie works for an OSPO
From writing a policy to the decisions it raises. Click through the four steps, or use the app itself.
Policies
Rules that gate findings at write, merge, and scan time, across OSS and cryptography. Definitions are shared across your organisation; this page shows the ones attached to this project.
| Policy | Action | Findings | Status |
|---|---|---|---|
| Block banned licensesOSS · edited 1 month ago | BLOCK | 0 | |
| Block high-severity vulnerabilitiesOSS · edited 1 month ago | BLOCK | 5 | |
| Block known exploited vulnerabilitiesOSS · edited 1 month ago | BLOCK | 0 | |
| Block reachable weak cryptographyCrypto · edited 1 month ago | BLOCK | 0 | |
| Block weak elliptic curvesCrypto · edited 1 month ago | BLOCK | 0 |
Scan Configuration
Controls how and when this project scans. They change what Earnie says and which paths it scans: never a verdict, a gate, or a finding already recorded.
On merge to payments-api’s default branch on GitHub.
Runs from the pre-commit hook appear in Self-checks for 30 days.
A coding agent’s earnie_review_code call checks code against the same policies before it lands.
Only on failure still refreshes an existing comment, so no stale red verdict stays up.
Lower severities stay visible in Earnie and in the summary.
Skip leaves a draft unscanned until it is marked ready.
payments-api
Can I merge?
Since baseline
Last 30 days across every workflow. Use it to see where policy holds, and where it needs work.
Reports
Frozen at generation and anchored to one scan.
| Template | Anchor | Formats | Download |
|---|---|---|---|
| Compliance | 9a91b12a | PDF · CSV | ↓ PDF ↓ CSV |
Defined once, checked everywhere
-
Write it once
Start from the built-in licence templates or build your own rule in the rule builder or in CEL. A policy can cover the whole organisation or only the projects where it has to differ, and it can start in Warn so you see what it would catch first.
-
People and coding agents alike
The Earnie CLI writes your policies into the file a coding agent reads for instructions, and supported agents have their changes checked when they finish each turn. Every change then meets the same policy at pre-commit and at merge, whoever or whatever wrote it.
-
Only what needs you
Earnie tells you when a policy gate fails, when an approval needs your decision and when one is decided: in its inbox and, through rules an Admin sets, by email, in Slack or Microsoft Teams, or through a webhook. Everything else stays in the record until you need it.
I write the rules once. Earnie applies them to every change, and I step in only when a decision needs me.
Write the policy once. Step in only when it matters.
Request a demo