Scan a Local Project for Exposed Secrets
Build a local-only scanner for fictional tokens, private-key markers, and risky environment files while handling false positives and never transmitting source code.
Build a local-only scanner for fictional tokens, private-key markers, and risky environment files while handling false positives and never transmitting source code.
Prepare 25m · Build 105m · Verify 25m · Document 25m
Work only inside the folder created by Smartphone-Academy.py prepare secret-exposure-scan. Use the supplied fictional samples or data you are explicitly authorized to handle.
Prepare the Termux workspace
Open Termux in the Academy folder and create the safe workspace. The companion generates samples, notes, and evidence files under your account.
python Smartphone-Academy.py prepare secret-exposure-scanNo root. Work only with the supplied files under $HOME.Practical mission
- Detect supplied fictional token formats, private-key markers, and suspicious environment assignments
- Exclude binary files, generated folders, and approved test fixtures with documented rules
- Redact secret values in reports while retaining enough evidence to locate the source
- Verify cleanup by rescanning a repaired copy and recording remaining limitations
A secret_scan.py tool, findings.json, allowlist.txt, and remediation-notes.md based on the supplied fictional project.
Quality gate
Analyst reflection
Which result from “Verify cleanup by rescanning a repaired copy and recording remaining limitations” needs additional evidence before it could support a real operational decision?
After checking the deliverables, run python Smartphone-Academy.py complete secret-exposure-scan. Progress is stored locally in the Termux home directory.