Agents write the code. You make the call.

Now in private beta. Free for beta teams while we work closely with each one.

Acme Engineering
Overview
Health
Release
Policies
212 of 500 runs this month
Overview · Components · GroupsTuesday 29 Sept
Compiled by AI from the live record.
Held at gates1
Awaiting approval1
Open findings11
Clean passes this month9
Awaiting your approvalApprove Checkout Service 4.2.0All checks cleared. Awaiting Release Manager approval · 2 days waiting
Request changesApprove the manifest
Needs your attentionapprovals, holds, recalls
HeldLegacy Auth Service 1.4.2 is held at Production. One Quality check needs attention.54 days
ApproveCheckout Service 4.2.0 is cleared and waiting on you.2 days
Recent outcomeslast 30 days
Shippedinventory-sync 3.8.0, a clean pass at Production. Good as gold.02 Sept
Shippedpartner-gateway-api 3.1.2 at Production, one waiver on the stamp.01 Sept
Notedbilling-ui 2.3.1 shipped with one noted finding, waived by R. Chen.28 Aug
Watches3 shipped versions watched. Nothing has changed since they shipped.Next check in 4 hours
This week40 versions checked. 38 cleared without a person. 1 noted, 1 held.
Lapsing soonjackson-databind on ledger-worker is waived until Thursday. Renew it or let it expire.

Your agents are shipping more code than you can read.

Cheer checks every change against your rules, surfaces what’s real and material, and cuts the rest of the noise.

Checks every push. Tests, scanners, AI reviewers, all validated against your policy and rules
It knows what a change touches. Ask about any package and you get the list of components, and what’s already been done about each.
It remembers what you decided. Waive a finding or adjust the severity to reduce the noise.
It stays out of your way. A clean result doesn’t need anyone. Most weeks, most of what ships never waits for a person.
Why now

More code, fewer readers, and the advisories keep coming

Pull request 2143Unreviewed
Authoragent/claude-code
Files changed40
Human reviews0
MergedTuesday 16:52
One of 61 this month merged with nobody reading it.
payments-api · this week412 commits
Carry an AI co-author173 · 42%
Reviewed by one person128
Reviewed by two9
Counted from commit trailers, not a survey.
AdvisoryCVE-2026-21744
Packagepkg:npm/undici
DisclosedWednesday 09:02
Exploit publishedThursday 11:40
Reaches4 of 31 components
Found by a frontier-model sweep of the library’s parser.
Findings across your scannersthis month
Raised1,204
Reachable and real31
Already waived by someone19
Need a person today3
The other 1,173 were settled without anyone.

Nine in ten developers now use AI to write code. About two fifths of what gets committed is AI-assisted.

DORA 2025. Sonar, State of Code 2026.

GitHub merged a record 519 million pull requests last year, up 29%, and says review is now the constraint. More gets merged with nobody reading it.

GitHub, Octoverse 2025.

Frontier models are finding upstream bugs by the tens of thousands, and an exploit now follows a disclosure in about a day.

NCSC via the Eclipse Foundation, May 2026. Palo Alto Networks, September 2026.

JFrog looked at the CVEs reported on the most-pulled Docker images and found 78% aren’t actually exploitable. Somebody still has to work out which.

JFrog Security Research, contextual analysis of DockerHub images.

You can’t hire your way out of this. Let Cheer settle the boring bits, and you focus on what’s real and material.

Week in the life

A week with Cheer

Tuesday arvo, 4:40

A 40-file PR from an agent

You open it expecting to lose the rest of your afternoon. It’s already been checked: CodeQL, Sonar and the tests, read against your policy. The one finding was waived last month by a teammate, with a date on it, so it isn’t flagged as new.

You read it for what it’s meant to do. That’s the only part that needs you. If the agent had run cheer check first, anything held would’ve been fixed before you ever saw it.

payments-api · PR 2143 · 40 files
Cleared
0114 checks passed.Cleared
02Known finding, waived until 14 Nov by S. Kaur. Doesn’t block.Noted
Not checked: whether it does what the ticket asked. That bit’s yours.Yours
Monday, first coffee

Two upgrades that matter, instead of a dozen Dependabot PRs

Over the weekend Cheer tried the available upgrades on each component, built them in a sandbox, and checked the result against policy. Only opened a valid PR where the results pass.

You merge the first, give the second another month with a one-line reason, and get on with your day. Nothing else was waiting for you.

Inbox2 items
payments-apiRefresh’s ready. 9 upgrades, built and checked. Clears 3 findings.Merge
ledger-workerYour waiver of jackson-databind runs out Thursday. Renew or let it go.Renew a month
Nothing else needs you. Knock off.
Wednesday, 9:15

A batch of advisories dropped overnight

A frontier-model sweep found a run of bugs in a popular HTTP library. Before anyone’s sat down, someone asks in the team channel: are we affected?

You run one command, and Cheer checks all four components, and tells you what’s real and what needs doing. Nobody spends the afternoon grepping lockfiles.

$ cheer reach pkg:npm/undici
4 of 31 components27 don’t carry it
01web-gateway upgraded Tuesday to 7.2.1Cleared
02notify-svc refresh PR openCleared
03billing-ui waived until 30 Oct by R. Chen: “not on the request path”Waived
04legacy-admin hasn’t been scannedNot scanned
What changes

Your reviewers get their afternoons back

payments-serviceService · TypeScript
Held at Production. Three checks need attention, one upgraded to critical.
Held
checkout-serviceService · Go
Cleared at Production. Waiting on the Release Manager.
Cleared
ledger-dbDatabase · Infrastructure
Clean pass. Quiet since the July migration.
Clean pass
legacy-adminWeb app · Python
Not scanned yet. Connect a source or hit Retrieve now.
Not scanned
Review what the change is for, not the hygiene.Tests, scanners and AI reviewers are read against your policy before you open the PR. You review the part that needs a person.
Unreviewed merges still get checked.When a PR merges without a review, the required check has still run against your policy.
Upgrades arrive built and checked.If an upgrade would break something, it doesn’t reach your queue.
Find out what an advisory touches in minutes.Named components, and what has already been done on each.
Decide once.A waived finding stays waived until the date you set.
Same rules for agents and people.Cheer applies the same policy to every change, whoever wrote it.
Only here

What you won’t get anywhere else

What does this touch?

Ask about a package, a library, a model version or one of your own APIs. You get the components it reaches and what’s already been done about each. Including the ones you haven’t scanned yet.

You decide once. It stays decided.

When you waive a finding, Cheer writes down who, why, and until when. It stops showing up as new, it runs out on its own, and you can look it up years later.

jackson-databind · MajorWaived
R. Chen, 14 Auguntil 30 Oct
“Not on the request path.”

Who wrote it, and who read it

Cheer counts AI co-authored commits and human reviews straight from git. No surveys, no guessing. It’s a number on every version.

41% of commits carry an AI co-author. Each was read by one person.

The CLI and git

It lives in git, where your code is

One small CLI. The record rides on the commit. Nothing new to learn. You get the same answer on your laptop, in your agent’s loop, and in CI.

For agents there’s a plugin: a skill that tells them when to run cheer check and what to do with a hold, and a read-only MCP server for questions like what’s open and what this touches.

An agent can flag a finding. It can’t waive one. That’s yours.

$ cheer check
Held. 1 of 12 checks needs attention.Held
01supply-chain-vuln-scan · stripe-node carries CVE-2026-21744, a remote code execution path in webhook parsing.Critical
02dependency-pinning · stripe is pinned to a floating minor range.Minor
10 cleared. Not checked: whether it does what the ticket asked.41 s
cheer checkWould this pass? Checks your working tree against the component’s policy and says in one sentence why anything’s held.
Required checkMerge is the first gate. One check reads the tests, scanners and reviewers against policy and comes back cleared, noted or held.
Stamp on the commitThe record rides with the code. At merge, the stamp is written to the commit as a trailer or a notes ref.
cheer verifyWas this signed off? Checks a commit’s stamp offline, on any forge.
cheer reachWhat does this touch? For any package, library, service or model: the components it reaches and what’s been done about each.
Humans and agents

Agents and automations prepare. You decide.

A clean result doesn’t take your attention
If Cheer pings you, it’s because only you can answer.
Make a decision with a click or overrule the AI
Everything is auditable and traceable with stamps added to the manifest as things happen
It tells you what it didn’t check.
It only sounds urgent when something needs you today.
The words

Seven words to learn. That’s the lot.

Everything else keeps its proper name inside the product, where the people who need it can find it.

checkone thing Cheer looks at
clearedthe check passed
notedseen, written down, not blocking
heldwaiting on a person
inboxonly what needs you, oldest first
clean passevery check ran, nothing held or noted
stampthe record, frozen at the gate

We’re letting teams in now. Want to be one of them?

Cheer is in private beta with a handful of teams running agents on every repo. Tell us about yours. We’ll get you set up and you’ll see your first clean pass on your own code. Nothing about how your team works changes until you say so.

checkout-service 4.2.0
Cleared
8 checks, 8 clear. Nothing held, nothing waived, nothing noted.
Waiting on the Release Manager at Production.