Enterprise DNAEnterprise DNA

Open Source · RAG

semantic-coverage

Automated detection of knowledge gaps and blind spots in RAG vector stores.

Our verdict

Not reviewed yet

We have not reviewed semantic-coverage yet

No one at Enterprise DNA has checked this listing against its sources. The description comes from public listings gathered automatically. Any fact below shows where it came from and when it was last checked.

How we review records

From the listing

About semantic-coverage

Semantic-coverage is an open-source Python tool that automatically detects knowledge gaps and blind spots in RAG vector stores. It analyzes the semantic coverage of a vector store to identify areas where the stored embeddings lack sufficient representation.

Best for

Developers building RAG systems who need to programmatically check vector store coverage and identify gaps.

Use cases

  • Audit a RAG vector store for missing or underrepresented topics
  • Identify blind spots in retrieval before deploying a RAG system
  • Validate the completeness of a knowledge base used for retrieval-augmented generation

Notes

12 stars on GitHub. Last updated 2025-12-24.

Pros

  • Focused specifically on RAG vector store observability
  • Open source with a permissive license
  • Lightweight Python library easy to integrate into existing pipelines

Cons

  • Very early stage with only 12 GitHub stars and limited community
  • No documented support for non-Python environments
  • May require manual tuning or additional tooling for production use

Key facts

What we have checked

Days since the last commit
324
Checked GitHub
GitHub forks
0
Checked GitHub
GitHub stars
13
Checked GitHub
Open issues
1
Checked GitHub
Releases in the last 90 days
0
Checked GitHub

Each value shows when we last confirmed it and where it came from. Values we have not confirmed are left out, never guessed.

Stars and usage

How semantic-coverage is growing

GitHub stars

12 to 13

stars. 12 July 2026 to 13 Nov 2026, 5 readings.

Source: GitHub. Checked .

Health and security

Is semantic-coverage looked after, and what do its setup files show

Health score

6 out of 100

Does someone look after this repository? It does not say the code is good or safe. Worked out from GitHub signals checked . How it is worked out

PartPointsWhat we saw
Recent activity3.7 of 30Last push 324 days ago
Releases0 of 150 releases in 90 days
Issue repliesNot countedThe latest check has no issue response reading (fewer than 3 measured issues, or issues switched off)
Maintainer0 of 15Owned by a single user
Official sourceNot countedMCP servers only

Sources

Where this comes from

  • GitHubRegistry

    Checked · Days since the last commit, GitHub forks, GitHub stars, Open issues, Releases in the last 90 days

A source shows what was published when we checked it. It does not certify security, performance or a working installation. Read our method.

Changelog

What changed

No changes recorded yet. Releases, price changes and deprecations appear here, with their dates, once we track them for this record.

Free 27-page guide

Get the free Developer’s Field Guide

A 27-page field guide to the AI coding workflow with Claude. Claude Code, MCP servers, the prompt patterns that work, and what to delegate. Free.

Enter your work email. We send it straight over, plus a few short notes worth knowing. Unsubscribe any time.

No spam. Unsubscribe any time.