Repository navigation
Issues and Support
Use GitHub Issues for bugs, provider requests, and real-account validation reports. Search existing issues and check Provider Coverage before opening a new one.
| You have | Use |
|---|---|
| Wrong data, a parsing failure, or a crate bug | Bug report |
| A live account check, including a successful match | Provider check |
| A new provider or an additional read-only data surface | Provider request |
| A vulnerability or possible credential exposure | Private security reporting |
For a bug, include the crate version or commit, operating system, Cargo features, provider, credential type, expected behavior, actual behavior, and the typed error. For a local CLI probe, include its version. A small Rust snippet or command with placeholder credentials is more useful than a large log.
For a provider check, say which quota windows, model labels, limits, resets, balances, or spend matched the provider's own usage page. Include the check date and whether it used the published crate or current source. Successful checks are valuable too.
Never post tokens, cookies, account IDs, credential files, screenshots containing secrets, or raw authenticated responses. If a provider response changed, describe its shape with redacted synthetic values. For security concerns, do not open a public issue with exploit details; follow the private process in SECURITY.md.
Want to fix an issue? See Contributing and Development.
Repository · Rust API docs · Issues · Releases · Security