CryoCore is designed to be public, but it sits near sensitive scientific and provider workflows. The main threats are accidental disclosure and false success.
- credentials, tokens, SSH keys, signed URLs, registry auth, provider secrets
- provider IDs, account IDs, billing records, pod logs, volume IDs
- private or unpublished structures, sequences, maps, masks, particle stacks, raw cryo-EM movies, model weights, and license files
- internal tracker content, local workstation paths, private image namespaces
.gitignoreblocks common scientific, credential, cache, and runtime outputs.public_snapshot_check.pyscans candidate files for heavy suffixes, private markers, and secret-like content.public_release_report.pyrequires public release files and blocks known public-switch markers.provider_closeout_check.pyrejects intent-only provider state.- GitHub issue and PR templates instruct contributors not to post sensitive material.
No scanner is complete. Before public switch, run make release-check, inspect
git status --short, and review any new files that touch providers, raw data,
license gates, or claim ledgers.
- Data Policy: the data tiers and git boundaries these controls enforce.
- Public Repo and Private Image Policy: the public source vs private runtime split.
- Public Switch Checklist: the readiness list before a public switch.
- No-False-Success Hardening: the closeout discipline that catches false-success exposure.