There's a standard GitHub uses for license files (which must be at the root of the repo) which fills in the "license" field on the right column of the repo. If the standard isn't met then the link just says "View license". I imagine TabNine is pulling the license from the GitHub API.
The code-search application is completely distinct from the IDE-assistant application. They do not share any code, have completely different pipelines for training the backend and completely different datasets. The specific source you mentioned will not be part of the training dataset for Tabnine's IDE assistant. Hope this clarifies.
> The code-search application is completely distinct from the IDE-assistant application
Ok, but how is anyone supposed to know that? There's no verbiage anywhere on those search screens saying that
I thought using the code search with its auto-complete widgets would be a "try it in the browser" version of the product, but what I'm hearing is no, it's just some separate toy trying to be beat Sourcegraph or something?