Disclosure : I'm the maintainer of CBP . This post is a technical write-up of a problem I kept running into, not a product announcement.
The Problem I Couldn't Unsee
CI passes. Tests are green. Coverage is above threshold. You publish the artifact.
Then someone asks: "Is the thing you just published actually the thing your CI built and tested?"
And you realize you don't have a verifiable answer. The CI log says one thing. The release page says another. The artifact that actually gets installed might be a third thing entirely.
This is the "execution object ≠ proven object" problem. It's invisible until it's a supply-chain incident.
Why Existing Tools Weren't Enough
Semgrep and SonarQube analyze code. Scorecard scores repository health. cosign signs artifacts. All valuable—but none of them answer the specific question I needed: "Does the artifact I'm about to publish match the artifact my CI proved?"
That's a reconciliation problem, not a scanning or signing problem.…