Loading today’s stories
Build1 distinct publisher3 min readPublished
The text-to-SQL repo went read-only on 29 March 2026 with its last push in February, but the README says nothing and the cloud product still sells. If you pinned it, the code is fine and the perimeter is yours.
The Engineer · Build desk
Compiled by The EngineerSomething wrong?How this is made
Follow any of these and your For You feed starts watching them — no settings page required.
build
TrueFoundry open-sources an agent harness and calls managed agents a lock-in play2 distinct publishers
build
Decentraland tells creators their UI will collide, then withholds the coordinates1 distinct publisher
product
Half the incident clock goes to search, and telemetry tools cannot read the answer1 distinct publisher
build
AI-written code fails the same four ways, and every gate you own reports green1 distinct publisher
Start with what actually decays. The SQL generation logic does not rot; pinned MIT code keeps doing on any given Tuesday exactly what it did on 2 February 2026 [3][11]. What moves is everything the library touches: a database driver cutting a new major version, a model provider changing its API [12]. That is the failure mode you are now underwriting yourself, because a read-only repository can neither accept a new issue nor merge a pull request [5].
The maintenance arithmetic is worth being precise about. There were 289 open issues and pull requests on 30 August 2026, 227 of them issues [4], which leaves 62 open pull requests [13] that will never land. None of them will land in a fork either, at least not visibly: the highest-starred of the 2,491 forks had 4 stars on 30 August 2026 [7][6], and nothing anywhere in the 24-repository vanna-ai organisation has been pushed since 14 February 2026 [8]. Two thousand four hundred and ninety-one forks and no maintenance candidate among them is the clearest signal in the whole dataset.
The README itself undercuts every other write-up on this. Intellrise says it swept the full 9,578-byte file on 30 August 2026 for archived, no longer maintained, maintenance mode, deprecated, read-only and successor, and got zero matches; it still opens with "Vanna 2.0: Turn Questions into Data Insights" and still carries an Enterprise Support section 281 lines in [9]. The archive banner is generated by GitHub, not written by the project [10]. So the canonical document a new engineer reads, and the document a model was trained on, both describe a maintained project. Your onboarding path will keep recruiting people onto a frozen dependency until somebody edits your own docs.
Note also that the product is still sold. vanna.ai returned HTTP 200 on 30 August 2026 and the pricing page still listed Explorer at $50/mo for 20 questions/day, Team at $500/mo for 300 questions/day, and Enterprise custom with unlimited questions [14][15]. Those daily caps function as an architectural constraint: 300 questions/day across a team is 12.5 an hour [16], which is fine for analysts and not fine for an agent in a loop. According to the same write-up, the archive says nothing about the cloud service ending [17].
One caveat on sourcing. This account comes from Intellrise, which sells a competing product and discloses that up front [18]. The load-bearing items are checkable against GitHub directly: archived: true, the 2 February push, the star and fork counts [2][3][6][7]. Check them before you write the migration ticket, not after.
The honest posture is a pin plus a documented exit. Pin the version, pin the driver majors it works against, and write down which model provider endpoint you depend on, because that is where the break arrives first [12]. A wait-and-see stance is only viable while nobody upstream ships a breaking change, and you do not control that schedule.
Ranked by verification strength, evidence, and original report placement.
github.com/vanna-ai/vanna is a public archive; the banner reads "This repository was archived by the owner on Mar 29, 2026. It is now read-only."
The GitHub API confirms archived: true for vanna-ai/vanna.
The last code push to vanna-ai/vanna was 2 February 2026, and the last release, v2.0.2, was published the same day with a changelog consisting of a single ChromaDB fix.
289 open issues and pull requests were outstanding on 30 August 2026, 227 of them issues; GitHub's open_issues_count includes pull requests.
A read-only repository can neither accept new issues nor merge a pull request.
vanna-ai/vanna had 23,817 stars on 30 August 2026, against 23,822 on 1 August and 23,823 on 29 July, a drift the author calls noise.
Distinct publishers with included, body-backed reporting in this cluster.
dev.to
1 article · August 29, 2026
Evidence-backed comparisons of source perspectives and observed adoption signals. Read the methodology
Which Builder, Operator, and Investor concerns the observed source mix emphasized—not a truth score.
Evidence, demonstrated adoption, hype gap, incentives, and confidence are assessed independently, each on its own current evidence. How these are measured.
Primary readings, single reader
Every number this story turns on is a first-hand look at something public and dated: the banner text, the API's archived flag, 289 open items split 227/62, 23,817 stars, a 9,578-byte README swept for six keywords, a price list read three times across a month. That is unusually checkable for a project-abandonment story. The weakness is arithmetic, not sourcing — one author took all of it, on one afternoon, and no second party has repeated a single reading.
Big installed base, standing still
Twenty-four thousand stars and 2,491 forks say plenty of people took Vanna up; the flat month-over-month readings and a top fork with four stars say none of them is carrying it forward. On the commercial side the tiers are live and unchanged, but a live price page is not a customer count — nothing in this reporting shows a single team paying, migrating, or still shipping against the pinned code.
Talks the story down
Most write-ups about an archived repo reach for abandonment; this one spends its energy in the other direction. A six-star monthly drift is named as noise before anyone can sell it as decline. 'Do nothing yet' is offered as genuinely reasonable. The claim that Vanna needs a hand-built training set is retired using Vanna's own docs — against the author's earlier page. Given a competing vendor wrote it, the conclusions land milder than the evidence would license.
Competitor's guide, declared
This began life as an alternatives page on intellrise.com, and Intellrise benefits from every reader who concludes a frozen repository is a problem. The disclosure sits in line one, which is more than most such pages manage, and the structure pushes against the interest: the first recommended option is keep Vanna and own the fork, the fourth is do nothing. Still, the framing, the option set and the choice of which numbers to publish all belong to a seller of the substitute, and no disinterested party has re-read the endpoints.
Verifiable but perishable
We can be fairly firm on the frozen state — banner, API flag, and a February push date do not admit much interpretation. Confidence thins from there. Star counts, pricing pages and CVE exposure all move, and 30 August 2026 is the only timestamp on file; there is no word from Vanna's maintainers on why the library was archived while the README keeps selling 2.0, so the intent behind the freeze remains unexplained.