privacy: scrub real hub paths/script names from public benchmarks#41
Merged
Conversation
The config-eval corpus (s8/s14/s17) and two benchmark docs had the author's real Claude Code hub pasted in: absolute C:\ClaudeCode\.claude\hooks paths, the actual guard-script names, the memory.jsonl path, and a personal C:\Users\davide checkout path. None are secrets, but they expose a private local setup in a public repo. Replaced with generic placeholders (./hooks/*.ps1, ./memory.jsonl, $env:TEMP, C:\path\to\whippet). The clean baseline scenarios stay clean — recall unchanged (96.5%), npm test green. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cosa
Rimuove dal repo pubblico i riferimenti al setup locale privato dell'autore, finiti dentro i benchmark.
Punti ripuliti:
benchmarks/config-eval/corpus.json(scenari s8/s14/s17) — path assolutiC:\ClaudeCode\.claude\hooks\*.ps1, i nomi reali degli hook-guard, eMEMORY_FILE_PATH→ placeholder generici (./hooks/*.ps1,./memory.jsonl).benchmarks/config-eval/README.md— riga "dogfood" che citava il path dell'hub →$CLAUDE_CONFIG_DIR.benchmarks/drift/PROTOCOL.md— path personaleC:\Users\davide\...eC:\ClaudeCode\.staging\...→C:\path\to\whippet/$env:TEMP\whippet-drift.Perché
Non sono segreti, ma espongono un setup locale privato (struttura cartelle, nomi degli script di sicurezza, posizione del file di memoria) in un repo pubblico. Niente di tutto ciò serve al plugin.
Sicurezza del cambiamento
Gli scenari "clean baseline" toccati restano puliti (0 findings): recall invariata 96.5%,
npm testverde, JSON valido.🤖 Generated with Claude Code