Vanna’s repository is archived while its product surfaces still look active

The main Vanna repository is archived. GitHub’s repository record marks it read-only, shows 23,821 stars and 2,485 forks, and dates the last push to February 2, 2026. That is a material maintenance signal for one of the most visible open-source text-to-SQL projects—even though the rest of Vanna’s public surface still reads like a current product.

The documentation remains online and introduces Vanna 2.0 as a user-aware AI agent framework that connects language models to databases. It describes tool execution, learned tool memory and permissions that flow through the system. The PyPI package page likewise presents Vanna 2.0 as an installable framework for natural-language-to-SQL, user-aware permissions, streaming tables and charts, and FastAPI or Flask integration.

GitHub’s release history puts the latest tagged version at v2.0.2, published on February 2. Its only listed change is a fix for unnecessary embedding-function initialization during ChromaDB collection retrieval. The repository still carries an MIT license, so archiving does not prevent users from forking or maintaining the code themselves. It does, however, prevent new issues, pull requests and repository changes unless the owner reverses the archive setting.

What users should do now

Do not interpret live documentation as evidence of active maintenance. Existing deployments should pin Vanna and its transitive dependencies, inventory open security and compatibility risks, and test a clean installation from the exact lockfile used in production. Teams evaluating Vanna should ask the maintainer whether development has moved to another repository or product before making the framework a long-lived dependency.

The project’s own migration notes make that diligence more important. Vanna 2.0 is described as a complete rewrite from the 0.x VannaBase API to an agent-based architecture, with a legacy adapter offered as a gradual bridge. A codebase that has already crossed a major compatibility boundary needs an explicit maintenance path; an archived repository with active-looking docs leaves that path unclear.

The nl2sql.ai directory now marks Vanna’s repository as archived while preserving its MIT license, current documentation link and latest verified release. That distinction matters: the software remains available, but availability and maintenance are not the same thing.