Guarantees
Keryn’s design carries five rejection tests. A feature that fails one is not built. They are written here as promises about the product, with the check that backs each. The statements are narrow on purpose.
A ranking always shows its edges
Section titled “A ranking always shows its edges”Keryn does not rank things by a risk score that hides the edges behind it. Every finding names its rule, file and line, its flow when a path was traced, its severity and its proof level as separate fields. In the Trust Canvas, a chokepoint or a Fix first entry states the chains it counts and the edge it concerns.
How it is checked: the Fix first sentence is built from the same edge and chain counts the analysis reports. The exported reports carry the fields separately. See paths, chains and chokepoints.
Nothing is uploaded by default
Section titled “Nothing is uploaded by default”Code and evidence stay where they were found: the browser tab, your machine, your CI runner. A scan of local files makes no network call; a repository scan downloads the repository from its host, or through api.keryn.app without storage if you chose the fast archive. Anything that leaves does so because you pressed a button that names the destination, and goes only to the address you configured.
How it is checked: the privacy page lists every network call the software can make, and a test compares that list with the code’s own list of allowed calls, so the two cannot drift apart. The pages for each connector say which fields travel and when. See local by design.
What it does not promise: a connector you configure and press sends what its page says to the host you chose. That host’s own handling is outside Keryn.
Every artifact is in the registry
Section titled “Every artifact is in the registry”An artifact that has no entry in the registry is not released, and this site shows only what the registry lists. Install and download pages are drawn from it, so they cannot name a package, a store listing or a download that does not exist.
How it is checked: the build of this site fails when a page names an artifact the registry does not list, or links a store listing the registry does not mark live. See downloads.
A verdict never changes proof and never closes a finding
Section titled “A verdict never changes proof and never closes a finding”A triage verdict is a second opinion recorded next to the evidence. It does not change a proof level, and nothing is closed, suppressed or dismissed without a recorded decision by a person.
How it is checked: verdicts and proof levels are separate fields in every output, and the site’s own prose check fails on wording that claims triage closes or dismisses findings. See agentic triage.
Explanations use mechanism, not metaphor
Section titled “Explanations use mechanism, not metaphor”Keryn describes what it does in terms of edges, evidence and proof. The explanation of what a feature is worth never leans on a story about the name or a symbol. The story of the name lives on the brand page and nowhere else.
How it is checked: the site’s prose check fails the build when a documentation page explains the product with a story about its name or a symbol.
When a guarantee is wrong
Section titled “When a guarantee is wrong”If a page here says something the product does not do, the page is wrong and the product is the authority. Say so in the public tracker once it exists. Until then, the limits page states what is measured and what is not.