zeekayandHanzo Dev
fc2375c584
The rename had left the repo half-named: README, CONTRIBUTING, SECURITY, Cargo.toml, the issue templates and docs all still said "Hanzo Search" and linked github.com/hanzoai/search. Two things were worse than stale. The README credited the upstream engine to "Index SAS" and said this repo is based on itself — a false attribution, fixed back to Meili SAS and meilisearch/meilisearch. And the docs shipped a TypeScript example importing `@hanzo/search`, a package that does not exist; it is now the `fetch` calls that actually work. `hanzoai/search-go` (a real repo) and `hanzoai/search-fts5` (named in the Dockerfile as where a build lesson came from) are deliberately untouched. Co-authored-by: Hanzo Dev <[email protected]>
1.4 KiB
Security
Hanzo AI takes the security of our software products and services seriously.
If you believe you have found a security vulnerability in any Hanzo-owned repository, please report it to us as described below.
Supported versions
As long as we are pre-v1.0, only the latest version of Hanzo Index will be supported with security updates.
Reporting security issues
Please do not report security vulnerabilities through public GitHub issues.
Instead, please kindly email us at [email protected]
Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:
- Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
- Full paths of source file(s) related to the manifestation of the issue
- The location of the affected source code (tag/branch/commit or direct URL)
- Any special configuration required to reproduce the issue
- Step-by-step instructions to reproduce the issue
- Proof-of-concept or exploit code (if possible)
- Impact of the issue, including how an attacker might exploit the issue
This information will help us triage your report more quickly.
You will receive a response from us within 72 hours. If the issue is confirmed, we will release a patch as soon as possible depending on complexity.
Preferred languages
We prefer all communications to be in English.