Free and Open Source, Distributed, RESTful Search Engine
Other / custom
There is a license file, but its text is not a standard license Reporight or GitHub recognizes. A human has to read it.
What this means for you
The signals do not agree or the text is not a recognizable standard license. Do not guess — read the evidence and get a human to decide.
You can
- Read the evidence below and check the source on GitHub
You must
- Have a person review the actual license text before you depend on this code
- Treat it as 'no permission granted' until that review lands
You cannot
- Assume it is permissive because the project looks like others that are
- Rely on Reporight's family guess here — there isn't one
This is not legal advice. Your obligations depend on how you use the code and your jurisdiction. Consult counsel for production risk.
How we know
- filenameLicense file found, text not recognized
The file does not match any reference license text Reporight carries. It may be custom, modified, or truncated.
- github apiGitHub declares 'Other'
GitHub found a license file but would not attribute it to a standard license — usually custom or modified text.
This summary reads the repository root only. Vendored trees and per-file headers can differ — run a deep scan to map every file.