Earnie

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.

Earniepayments-api 2OLospo.lead
payments-api / Policies

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.

All policiesApprovals0
Search policies 5 of 5 policies
PolicyActionFindingsStatus
Block banned licensesOSS · edited 1 month agoBLOCK0
Block high-severity vulnerabilitiesOSS · edited 1 month agoBLOCK5
Block known exploited vulnerabilitiesOSS · edited 1 month agoBLOCK0
Block reachable weak cryptographyCrypto · edited 1 month agoBLOCK0
Block weak elliptic curvesCrypto · edited 1 month agoBLOCK0

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.

Skip patternsComponent overridesInherited layers
Automatic scanningApplies on the next merge

On merge to payments-api’s default branch on GitHub.

Pre-commit and coding agentsSelf-checks
Pre-commit hook

Runs from the pre-commit hook appear in Self-checks for 30 days.

earnie hook install
Coding agents over MCP

A coding agent’s earnie_review_code call checks code against the same policies before it lands.

Pull-request feedbackApplies on the next pull-request scan
Summary comment

Only on failure still refreshes an existing comment, so no stale red verdict stays up.

Inline comment floor

Lower severities stay visible in Earnie and in the summary.

Draft pull requests

Skip leaves a draft unscanned until it is marked ready.

payments-api

Full coverageRepository scan · Scanned 2 hours ago
OverviewComponentsCryptography
Can I merge?
Merge gatescan 42
Blockedon 2 policy results
Block 2Approval 14Warn 9Pass 1,284
Needs attentionone verb each
Blocked2 policy results block a merge on this project.
Approval14 policy results require approval before a merge.
Warned9 policy results warn; merge is allowed, the record is not clean.
Ambiguous3 components carry no license assertion.
EvidenceNo SBOM snapshot exists for the current scan.

Since baseline

Last 30 days across every workflow. Use it to see where policy holds, and where it needs work.

Closed by agents / CIby week
37
License approvalsrequested
14
Export evidenceresolved
90%

Reports

Frozen at generation and anchored to one scan.

TemplateAnchorFormatsDownload
Compliance9a91b12aPDF · 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
Earnie for OSPO leads
Earnie

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.

Earniepayments-api 2OLospo.lead
payments-api / Policies

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.

All policiesApprovals0
Search policies 5 of 5 policies
PolicyActionFindingsStatus
Block banned licensesOSS · edited 1 month agoBLOCK0
Block high-severity vulnerabilitiesOSS · edited 1 month agoBLOCK5
Block known exploited vulnerabilitiesOSS · edited 1 month agoBLOCK0
Block reachable weak cryptographyCrypto · edited 1 month agoBLOCK0
Block weak elliptic curvesCrypto · edited 1 month agoBLOCK0

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.

Skip patternsComponent overridesInherited layers
Automatic scanningApplies on the next merge

On merge to payments-api’s default branch on GitHub.

Pre-commit and coding agentsSelf-checks
Pre-commit hook

Runs from the pre-commit hook appear in Self-checks for 30 days.

earnie hook install
Coding agents over MCP

A coding agent’s earnie_review_code call checks code against the same policies before it lands.

Pull-request feedbackApplies on the next pull-request scan
Summary comment

Only on failure still refreshes an existing comment, so no stale red verdict stays up.

Inline comment floor

Lower severities stay visible in Earnie and in the summary.

Draft pull requests

Skip leaves a draft unscanned until it is marked ready.

payments-api

Full coverageRepository scan · Scanned 2 hours ago
OverviewComponentsCryptography
Can I merge?
Merge gatescan 42
Blockedon 2 policy results
Block 2Approval 14Warn 9Pass 1,284
Needs attentionone verb each
Blocked2 policy results block a merge on this project.
Approval14 policy results require approval before a merge.
Warned9 policy results warn; merge is allowed, the record is not clean.
Ambiguous3 components carry no license assertion.
EvidenceNo SBOM snapshot exists for the current scan.

Since baseline

Last 30 days across every workflow. Use it to see where policy holds, and where it needs work.

Closed by agents / CIby week
37
License approvalsrequested
14
Export evidenceresolved
90%

Reports

Frozen at generation and anchored to one scan.

TemplateAnchorFormatsDownload
Compliance9a91b12aPDF · 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