A test key almost shipped in a public repo. The secret scanner caught it first.

What we did

One of the five tools we made public today has its source in a public repo. Before it went public, the secret scanner ran over the repo.

What we believed

The repo was ready to publish as it was.

What reality said

The secret scanner caught a test key that KvK publishes officially in its docs. We changed it to an environment variable, and only then did the tool go public.

What changed

Making a tool public is also a code-review step, and the scanner is the cheapest reviewer we have.

Explicit non-claims

• The key is KvK's official public test key for its test environment; it is not quoted here.
• This entry makes no revenue or customer claim.