Weir

It reads the OpenTelemetry traces your agent already emits and fails the build when sensitive data reaches a sink it should not reach.

Did sensitive data flow through the agent to a sink it should never have reached?

Your agent already answers that question in the traces it emits. Weir reconstructs the session graph, tracks taint through it, and shows the evidence node by node.

Most exports fail this first step, because content capture ships off by default almost everywhere. So weir names the exact switch to flip, read from the instrumentation in your own trace.

Exit 1 , build fails, secret redacted. That finding came from one rule, and a rule is just a file. This is the whole thing:

No code, no DSL. You name a source, a sink, and a mode. The engine builds the graph, tracks the taint, and shows its work.

Rewording your prompts will not move a finding. Adding a step will not move it. If the evidence genuinely weakens, the finding is demoted and says why, instead of quietly flipping to green.

It reads real traces, not ones we wrote. The suite pins a frozen capture that no weir code ever touched ( provenance ). Broken input degrades under one of 18 named rows; it never guesses ( contract ).

Attacker content cannot rewire it. Joins follow evidence tiers, and a finding that crosses a weak one is never verdict-grade.