chore: replace generic emails with GitHub references

[CybotTM]

Summary

• Replace generic @netresearch.de email addresses with GitHub-native references
• Add support section to package metadata with Issues/Source URLs
• Use GitHub Security Advisories for vulnerability reporting
• Use GitHub Issues for general support/contact

Motivation

Generic email addresses in public repositories attract spam and create maintenance overhead. GitHub provides better mechanisms for each use case:

• Security: Private vulnerability reporting via Security Advisories
• Support: Issue tracker with templates and labels
• Contact: Discussions for general questions

Test plan

• Verify package metadata is valid (composer validate)
• Verify links in documentation point to correct URLs
• Verify no functional email addresses were removed (only metadata/docs)

[gemini-code-assist]

Summary of Changes

Hello @CybotTM, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request modernizes the project's communication channels by transitioning from generic email addresses to GitHub's integrated features. The primary goal is to enhance security vulnerability reporting and general support by leveraging GitHub Security Advisories and Issues, thereby reducing spam and streamlining maintenance overhead.

Highlights

• Security Contact Update: Replaced the direct email address for security vulnerability reporting in CONTRIBUTING.md with a link to GitHub Security Advisories.
• Enhanced Communication Channels: Shifted communication channels from generic email addresses to GitHub-native features, aiming to reduce spam and improve issue management.

Changelog

• CONTRIBUTING.md
  • Updated the security contact method from an email address to a link to GitHub Security Advisories.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates the CONTRIBUTING.md file to replace a generic security email address with a link to GitHub Security Advisories. This is a good practice that centralizes security reporting through GitHub's dedicated feature, which helps in tracking and managing vulnerabilities privately and effectively. The change is correct and aligns with the goal of modernizing contact and support channels for the project. The implementation is sound and I have no further recommendations.

[Copilot]

Pull request overview

Replace public email-based contact points with GitHub-native support and security reporting links to reduce spam and standardize contribution workflows.

Changes:

• Updated security contact in contributing docs to point to GitHub Security Advisories (private reporting flow)

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The link points specifically to the new advisory / report flow, but the label 'GitHub Security Advisories' can read like it points to the advisories list. Consider renaming the link text to something more explicit (e.g., 'Report a vulnerability' or 'Security advisory (report)') to better communicate the action contributors should take.

Suggested change

	- **Security**: [GitHub Security Advisories](https://github.com/netresearch/phpbu-docker/security/advisories/new)
	- **Security**: [Report a security vulnerability](https://github.com/netresearch/phpbu-docker/security/advisories/new)