Top AI Repos — open-source AI, indexed and scored
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Open Source research tool to search, browse, analyze and explore large document collections by Semantic Search Engine and Open Source Text Mining & Text Analytics platform (Integrates ETL for document processing, OCR for images & PDF, named entity recognition for persons, organizations & locations, metadata management by thesaurus & ontologies, search user interface & search apps for fulltext search, faceted search & knowledge graph)
| Date | Stars |
|---|---|
| 2026-07-24 | 1190 |
| 2026-07-25 | 1190 |
| 2026-07-28 | 1190 |
| 2026-07-30 | 1190 |
| 2026-07-31 | 1192 |
| 2026-08-06 | 1192 |
Today
— stars today
This week
+2 stars this week
This month
— stars this month
Momentum
0.0
growth rate 0.17%/day
# Open Semantic Search https://opensemanticsearch.org Open Semantic Search is: - an integrated search server, - ETL framework for document processing (crawling, text extraction, text analysis, named entity recognition and OCR for images and embedded images in PDF), - search user interfaces, text mining, text analytics and search apps for fulltext search, faceted search, exploratory search and knowledge graph search # Documentation This README.md is documentation for software developers. ## Documentation for users and admins The [documentation for users and admins](docs/doc/README.md) is included in the software packages/images and linked in the search user interface (Menu "Help"). ## Software architecture You can find the [documentation of the search engine architecture in `docs/doc/modules/README.md`](docs/doc/modules/README.md). ## Documentation format This integrated HTML [documentation](https://opensemanticsearch.org/doc/search/) is generated by the static site generator [MkDocs](https://www.mkdocs.org/) with the config file [`mkdocs.yml`](mkdocs.yml). The source of the documentation (Markdown format) and the charts ([mermaid](https://mermaid-js.github.io/mermaid/) format) is editable in the directory [`docs`](docs). # Build How to build the deb package for installation on Debian or Ubuntu server or the docker images for running in Docker containers: ## Clone git repositories Clone the repository including the dependencies: ``` git clone --recurse-submodules --remote-submodules https://github.com/opensemanticsearch/open-semantic-search.git cd open-semantic-search ``` ## Build deb package To build a `deb` package for *Debian GNU/Linux* or *Ubuntu Linux*, call the build script <code>[build-deb](build-deb)</code> as user root (change user by `su` or `sudo su`): ``` ./build-deb ``` ## Build Desktop Search VM How to build an *Open Semantic Desktop Search* Appliance for *VirtualBox* is documented in [`src/open-semantic-desktop-search/README.md`](src/open-semantic-desktop-search/README.md). ## Build docker images Build the Docker images using the default docker-compose config <code>[docker-compose.yml](docker-compose.yml)</code>: ``` docker-compose build ``` ## Run docker containers After these builds all the Docker images/dependencies/services can be started together by docker-compose with the config file <code>[docker-compose.yml](docker-compose.yml)</code>. You can start the whole environment by running: ``` docker-compose up ``` which will expose the web user interface on port `8080`. You can browse the Open Semantic Search user interface in your favourite browser by this URL: `http://localhost:8080/search/` # Automated tests For CI/CD there are some different automated tests: ## Integration tests Since the [submodule Open Semantic ETL](src/open-semantic-etl) uses and needs different powerful services like [Solr](src/solr.deb), [spaCy-services](src/spacy-services.deb) or [Tika-Server](src/tika-server.deb) by HTTP and REST-API, many automated tests run as integration tests within the docker-compose environment configured in <code>[docker-compose.etl.test.yml](docker-compose.etl.test.yml)</code> so these services are available while running the unittests and integration tests. ``` docker-compose -f docker-compose.etl.test.yml build docker-compose -f docker-compose.etl.test.yml up ``` ## End to end tests Some automated integration tests and end-to-end (E2E) tests within a web browser controlled by the browser automation framework [Playwright](https://playwright.dev/) and the node.js / javascript based test framework [JEST](https://jestjs.io/). You can extend the automated tests in <code>[test/test.js](test/test.js)</code> They run by the docker image <code>[Dockerfile-test](Dockerfile-test)</code> and need the services of the docker-compose environment <code>[docker-compose.test.yml](docker-compose.test.yml)</code>: ``` docker-compose -f docker-compose.test.yml build docker-compose -f d
Excerpt of 6,743 characters
Read on GitHub
292
14
9
6
2
2
1
1
1
Would you bet a product on this? Bounded 0–100 and slow moving.
matched fp:f9cdb25e2d852126, topic:ocr, desc:etl, readme:etl
matched fp:f9cdb25e2d852126, topic:named-entity-recognition, desc:named entity recognition, readme:named entity recognition