fix: replace stale [email protected] contact email#61
Open
chaksaray wants to merge 1 commit into
Open
Conversation
Swept SECURITY.md, CODE_OF_CONDUCT.md, CONTRIBUTING.md, and docs/specs/ave-implementer-guide.md for the old contact address, replaced with [email protected]. GOVERNANCE.md, README.md, and package.json do not contain it -- confirmed via discovery grep rather than assumed from the likely-locations list. SECURITY.md had two occurrences in genuinely different contexts: one for reporting vulnerabilities in Bawbel's own tooling (scanner, PiranhaDB, ave-site), one for the AVE standard's own critical/ pre-disclosure record-submission contact (explicitly distinguished in the file's own prose as "not a Bawbel security report"). Both changed to the new address per explicit confirmation.
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.
Summary
Discovery (`grep -rln "[email protected]" .`) found 4 files, not the 6 the original brief guessed -- `GOVERNANCE.md`, `README.md`, and `package.json` don't contain it.
`SECURITY.md` needed a judgment call: it uses the address in two genuinely different contexts -- one for reporting vulnerabilities in Bawbel's own tooling (scanner, PiranhaDB, ave-site), one for the AVE standard's own critical/pre-disclosure record-submission contact, explicitly distinguished in the file's own prose ("not a Bawbel security report"). Confirmed with the maintainer that both should move to the new address.
No Bawbel-attributed language needed rewriting beyond the address itself -- all 4 occurrences were plain "email X" phrasing, not "Contact Bawbel at X."
Test plan