Harden public showcase privacy controls
Some checks failed
public-safety / privacy-and-secret-scan (push) Has been cancelled
Some checks failed
public-safety / privacy-and-secret-scan (push) Has been cancelled
This commit is contained in:
@@ -31,9 +31,9 @@ Removing a value from the latest commit does not remove it from Git history.
|
||||
|
||||
## Repository controls
|
||||
|
||||
The public repository uses two checks:
|
||||
The public repository uses layered checks:
|
||||
|
||||
- `scripts/check-public-safety.py` rejects infrastructure identifiers, private paths, key-like files, and common secret patterns.
|
||||
- `scripts/check-public-safety.py` rejects infrastructure identifiers, private paths, key-like files, binary files, raw-export filenames, non-approved URL hosts, and common secret patterns. Its source is executed and syntax-checked rather than matched against its own detector literals.
|
||||
- Gitleaks scans complete Git history in CI.
|
||||
|
||||
The scanner is deliberately conservative. Placeholder examples should use unmistakable values such as:
|
||||
@@ -64,4 +64,4 @@ https://service.example.net
|
||||
|
||||
## Reporting
|
||||
|
||||
Do not open a public issue containing a suspected secret. Revoke it first and use a private contact channel for disclosure.
|
||||
Do not open a public issue containing a suspected secret. Revoke it first, then use [GitHub private vulnerability reporting](https://github.com/fizzlepoof/homelab-showcase/security/advisories/new). The repository owner may also be contacted through an already established private channel.
|
||||
|
||||
Reference in New Issue
Block a user