Dev.Can-Make-Public

Workflow

1. Confirm scope

   • Identify the repo root and whether it is a git repository.
   • If git history exists, plan to scan both working tree and history.

2. Scan working-tree filenames (high-signal)

   • Look for common secret/credential files and key material by filename.
   • Example:

rg --files -g '.env*' -g '*.pem' -g '*.key' -g '*.p12' -g '*.pfx' -g '*.jks' -g '*.keystore' -g '*id_rsa*' -g '*id_ed25519*' -g '*.npmrc' -g '*.pypirc' -g '*credentials*' -g '*secret*' -g '.aws/credentials'