Skip to content
Watchdog
Sign inSurvey a repo free

For software owners

Know the quality of the code you own.

When consultants, an outsourcing partner or a supplier build a company's systems, the company owns the code, but usually the only regular report on its quality comes from the people who wrote it. That holds even when the owner can read code, because many technical owners have no access to the code or no time to read it.

Watchdog surveys the code on a schedule, independently of the supplier, and grades it from 0 to 100, whatever stack it is built in. That score is the Code Assurance Index, an open standard whose rules are published. The owner gets the number and the evidence behind it, whoever writes the code.

Sign in with GitHub, GitLab, Bitbucket or Azure DevOps · no card · the first survey of every repository you connect is free.

Independent

of the supplier, and the supplier doesn't have to change anything in how it works

4

full reports with every survey, written for leadership, engineering, security and audit

Same score

the owner and the supplier see the same number, and either of them can check how it was worked out

€0

for the first survey of every repository you connect, with nothing held back

What a demo can't show

What an owner needs to know about the code.

A demo shows what the software does. A survey shows how well it is built, and answers the questions that matter to an owner. Every survey comes with four reports, written for leadership, engineering, security and audit, which the evidence page describes in full.

Could the owner change supplier?

The survey shows which parts of the code only one or two people know (the bus factor), how tightly its parts depend on each other, and how much of the code nothing uses. Together they decide whether the owner can change supplier, or depends on the current one.

Is it secure, and can the owner show it?

The survey looks for libraries with publicly known vulnerabilities (CVEs), passwords and keys committed at any point in the code's history, and unsafe settings in container and cloud configuration. It also collects the evidence a tool can provide for regulations such as NIS2, the Cyber Resilience Act and DORA.

Is it getting better or worse?

Surveys on a schedule, such as every sprint, measure the code the same way each time. The owner sees how the score moves over time, and supplier reviews start from numbers both sides can see.

Does the delivery meet what was agreed?

The owner and the supplier can agree a minimum score in the contract. The audit report then shows whether each delivery meets it, which version of the code and of the rules was measured, and what changed since the last survey. It carries the signed record of the result.

How it fits in

Watchdog works alongside the supplier.

Nothing changes for the supplier

Watchdog reads the code on its own machines, on a schedule. Nothing runs in the supplier's own systems, so the supplier's work is never slowed down or stopped, and the supplier doesn't have to change how it works.

The supplier can check the score too

The rules behind the score are published, and anyone can work out the score again from the evidence. The supplier sees the same number as the owner, so both sides talk about the same facts.

Watchdog and Assay answer different questions.

Watchdog shows how good the code a company owns is, and whether it is getting better. It makes no difference who writes the code: the company's own developers, a supplier or a consultancy. The company owns the code in each case, so it connects the repositories and uses Watchdog.

Buying software raises a different question. Before a company buys a packaged system, or acquires another company along with its systems, it doesn't own that code yet, and what it needs to know is whether the software is worth buying. That is the job of Assay, our product for business reports. Assay checks the software before the purchase, and its report shows the people who decide what they would be buying.

Assay also helps with code a company already owns. When the people who decide want to know what a survey's findings mean for the business, Assay writes that report from the Watchdog survey, in plain language. The report covers, for example, the risks in the findings and what it costs to leave them unfixed.

Many organisations use both: Watchdog to measure the systems built for them, and Assay before they buy software, or when they need a report on their own code.

Measure what you are paying for.

The first survey of every repository you connect is free, so you see the result for your own code before you pay anything. After that, every price is on the pricing page.

Next: From code host to your first baseline · Answers for your security reviewer, or browse all the guides.

Building the software with your own team? See Watchdog for engineering teams. Building software for clients? See Watchdog for consultancies and freelancers.