Skip to content

fix: replace stale [email protected] contact email#61

Open
chaksaray wants to merge 1 commit into
developfrom
fix/contact-email-sweep
Open

fix: replace stale [email protected] contact email#61
chaksaray wants to merge 1 commit into
developfrom
fix/contact-email-sweep

Conversation

@chaksaray

Copy link
Copy Markdown
Contributor

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` (2 occurrences), `CODE_OF_CONDUCT.md`, `CONTRIBUTING.md`, `docs/specs/ave-implementer-guide.md` swept to `[email protected]`

`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

  • `grep -rln "[email protected]" .` -- zero results
  • `grep -rln "[email protected]" .` -- 4 files (5 occurrences, SECURITY.md has 2)
  • `python3 scripts/validate_records.py` -- all 59 records still valid (this PR touches no records)

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant