public-repo-safety

To scan for secrets and PII before a public release, run a preflight pass on your workspace to identify tracked files containing credentials, personal identifiers, and local absolute paths. This produces a file-scoped blocker report detailing exact locations for remediation.

Public repo safety scanning identifies public-release risks like secrets, personal data, and unsafe artifacts in your codebase. You need it before pushes, releases, PRs, or publish-ready docs to prevent accidental exposure of sensitive information outside the private workspace.

Yes, preflight repo scanning evaluates both tracked files and qualified untracked artifacts that could become public. This ensures unsafe screenshots, internal prompts, and local paths are caught even if they have not yet been committed to version control.

Stop accidental artifact promotion by enforcing blocker categories for unsafe screenshots and internal prompts during your preflight scan. The scan produces a pass/fail report with exact blocker locations to halt public release until issues are resolved.

The best way to identify local absolute paths is executing a preflight workspace scan targeting public-release safety. This flags local paths alongside secrets and personal data, providing a concise blocker report suitable for remediation decisions before any push.

Your preflight scan fails because it detected blocker categories like secrets, personal data, local paths, or unsafe screenshots. The scan enforces a strict pass/fail check, generating a file-scoped report of exact locations that must be remediated before release.