Skip to content

chore: remove maintainer personal email from public files#20

Merged
tamimbinhakim merged 1 commit into
masterfrom
chore/scrub-maintainer-email
Jun 6, 2026
Merged

chore: remove maintainer personal email from public files#20
tamimbinhakim merged 1 commit into
masterfrom
chore/scrub-maintainer-email

Conversation

@tamimbinhakim

Copy link
Copy Markdown
Contributor

Removes the maintainer's personal email from public-facing files (it would otherwise publish to crates.io via Cargo.toml authors and render on the repo).

File After
Cargo.toml author name only, no email
SECURITY.md report via GitHub Security Advisories (private reporting)
CODE_OF_CONDUCT.md conduct reports via Security Advisories (interim)
GOVERNANCE.md advisors reach out via GitHub Discussions

All real, working private channels — nothing fabricated — swappable for a dedicated contact email later.

Not touched: existing commit history still carries the old author email. A clean erase isn't possible (force-push to protected master + GitHub caches old commits), so it's left as-is by request. Future commits already use the GitHub noreply address.

🤖 Generated with Claude Code

Replaces the maintainer's personal email in public-facing files with private,
non-email channels so it isn't published (crates.io author metadata) or shown
on the repo. A dedicated contact email will replace these placeholders later.

- Cargo.toml: author name only, no email
- SECURITY.md: report via GitHub Security Advisories (private reporting)
- CODE_OF_CONDUCT.md: conduct reports via Security Advisories (interim)
- GOVERNANCE.md: advisors reach out via GitHub Discussions

Note: existing commit history still carries the old author email; rewriting it
would require a force-push to protected master and GitHub still caches old
commits, so it is intentionally left as-is. Future commits use the GitHub
noreply address.
@tamimbinhakim tamimbinhakim merged commit f830ca7 into master Jun 6, 2026
5 checks passed
@tamimbinhakim tamimbinhakim deleted the chore/scrub-maintainer-email branch June 6, 2026 06:45
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