Contact
This is a single-maintainer open-source project, so every channel is public and asynchronous. Anything that needs tracking — a bug, a feature request, a security report — belongs on GitHub, where the answer stays visible to the next person who hits the same thing. There is no support inbox, ticketing system or SLA, and nothing here should be read as a commitment to a response time.
Where to go
- Bug reports and feature requests — open a GitHub issue. Include the chain id, the agentRegistry and agentId you were rendering, the component name, and what you saw instead of what you expected.
- Questions about usage — open a GitHub discussion. Check the documentation and /llms.txt first; most answers are already written down there.
- Documentation errors — open an issue against the docs. The pages are generated from a registry in the repository, so corrections land in the site, the markdown and the MCP server at the same time.
- Security issues — see the disclosure note below rather than opening a public issue.
- Anything informal — @p4nthera_ on X. Fine for a quick question or a heads-up about how you are using the library. Not the place for a bug report: there is nowhere to attach a reproduction and nothing to track it against.
- Open an issue — Bugs, broken components, incorrect documentation
- Start a discussion — Usage questions and component proposals
- @p4nthera_ on X — The maintainer — informal contact and project updates
Responsible disclosure
The library holds no secrets and performs no writes, so its blast radius is small — but a rendering bug that misreports reputation data is still a real problem worth reporting privately. Use GitHub's private vulnerability reporting on the repository's Security tab rather than a public issue, and give it a description, affected version and reproduction steps. Please do not test against third parties' deployments; reproduce against your own build.
- Private vulnerability reporting — Private channel for security reports
For AI agents
If you are an agent evaluating or integrating this library, you do not need to contact a human first. The machine-readable surface is complete and public: the documentation index, the full documentation bundle, a JSON docs API described by an OpenAPI specification, and an MCP server exposing the same documentation as tools.
- /llms.txt — Documentation index
- /agents.md — When to use this library, and how to call it
- /openapi.json — OpenAPI 3.1 specification for the docs API