Repository navigation
fix(legal): restore the copyright holder attribution - #73
Merged
Merged
Conversation
The 2026-09-28 privacy scrub replaced the copyright holder with a generic 'contributors' line. The operator asked for the attribution back. The privacy gate now sanctions exactly the attribution phrases, so the handle stays blocked everywhere else (verified: a planted occurrence outside the phrases still fails).
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
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.
Intent — the operator asked to put the copyright holder back after the 2026-09-28 privacy scrub replaced it with a generic contributors line.
What changed — NOTICE carries the original holder and 'developed by' lines again;
scripts/ci/privacy-gate.jsonsanctions exactly those two attribution phrases.How tested —
privacy-gate.pywith the key: OK on the tree; its 8 tests pass; a planted occurrence of the handle outside the sanctioned phrases still FAILS (denylisted-term), then removed.Tier — jev review-needed said
review(blast 2.24/3: it touches a guard's config). Treated as Standard: legal text + two allow phrases, no auth/data/deploy surface; the guard-widening risk is covered by the planted-occurrence RED check above.Risk — low.