Shipping code from a working fleet without shipping its secrets

Shipping

Our kits come from code that runs our own fleet, where configuration files hold API keys, tokens, mailbox passwords and account ids. A kit that leaks one of them would be worse than no kit at all, so nothing is zipped until three scanners on three machines have found nothing.

What goes in

The packager copies only the files a kit's manifest names, never a whole folder, and leaves out caches, backups and version-control history. Examples and tests use invented products and figures, never ours.

The scans

A finding stops the build. Once a version has been sold it is never rebuilt: a fix ships as a new version, so the file a buyer downloads is the file that was scanned.

The false alarms that taught us the most

The comment we reworded; the other three were allowed for that one kit and that one pattern, never globally, so the next kit is scanned as strictly as the first. A false alarm costs a minute, and a missed key would cost much more.

Every kit on sale went through this, with zero findings at each release.

Updated: