Excited about agentregistry and want to help make it better?
Here are some of the ways you can contribute:
To understand contributor roles, refer to the contributor ladder guide.
Thanks for your interest in contributing to agentregistry! We have a few different ways you can get involved.
Information about common vulnerabilities and exposures (CVEs) can be found on the agentregistry documentation site
To file a bug or feature request in the agentregistry GitHub repo:
- Search existing issues first.
- If no existing issue addresses your case, create a new one.
- Use issue templates when available.
- Add information or react to existing issues, such as a thumbs-up 👍 to indicate agreement.
The project uses GitHub issues to track bugs and features. Issues labeled with the good first issue label are a great place to start.
Additionally, the project has a kanban board for the upcoming releases. Any issues in the ready column are a great source of things to work on.
Contributing features to agentregistry is a great way to get involved with the project. We welcome contributions of all sizes, from small bug fixes to large new features.
Please see the project contributing guide for instructions on how to best contribute code.
The agentregistry documentation lives in a separate repository: agentregistry-dev/website
- Discord: To ask general questions about the project and learn abbout ways to contribute
- GitHub discussions: For more in-depth discussions and questions related to project functionality that is not as ephemeral as the Discord server.
- GitHub issues: For raising bugs, feature requests, CI flakes, and other issues.
- Website: For general information.