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 aims to modernize and streamline communication channels by replacing outdated generic email addresses with more efficient and integrated GitHub-native mechanisms. The changes reduce potential spam and maintenance overhead by leveraging GitHub's built-in features for security advisories, issue tracking, and general discussions, thereby improving the overall support and contact experience for users and contributors.

Highlights

• Contact Information Update: Replaced generic email addresses with GitHub-native references for author contact information.
• Package Metadata Enhancement: Added a dedicated 'support' section to the package metadata, including URLs for issues and source.
• Vulnerability Reporting: Shifted the recommended method for vulnerability reporting to GitHub Security Advisories.
• General Support and Contact: Designated GitHub Issues as the primary channel for general support and contact.

Changelog

• .claude-plugin/plugin.json
  • Updated the author's contact from an email address to a GitHub repository URL.
  • Introduced a new 'support' object with an 'issues' URL pointing to the GitHub issue tracker.

Activity

• No activity has occurred on this pull request yet.

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

The pull request successfully replaces the generic email address with a GitHub repository URL in the author metadata and introduces a dedicated support section with an issues URL. This change aligns well with the motivation to reduce spam and leverage GitHub's native mechanisms for support and contact, improving maintainability and security. The changes are clear and directly address the stated goals of the pull request.