textgen vs lingbot-map

textgen and lingbot-map share 4 technologies: Hugging Face, einops, safetensors, and pillow. Both are written in Python.

Read it as markdown

What they share and what sets them apart

In common

Robbyant

lingbot-map

[ECCV 2026 Best Paper Award Candidate] LingBot-Map: Geometric Context Transformer for Streaming 3D Reconstruction

Python18.6kRead on November 6, 2026, at commit b9dd1b1What is lingbot-map built with?

Only in lingbot-map

Side by side

SizeLines written by people and agents, without generated ones; code files, without tests.
textgen29,113 lines written105 code files
lingbot-map36,798 lines written64 code files
Who writes itA commit counts as AI's when it carries its signature: a Co-Authored-By line, its author name or the merge of its branch.
textgen0% of its commits signed by AIWith GitHub Copilot
lingbot-map0% of its commits signed by AI
ActivityFrom GitHub and its history, on the day SeeRepo read it.
textgenLast push August 17, 20265,288 commits47,737 stars
lingbot-mapLast push October 14, 2026123 commits18,556 stars
TestsThe files that test the code, and the share of code files a test imports.
textgen1 test file1% of its code files have a test that imports them
lingbot-map0 test files

Frequently asked questions

Which is bigger, textgen or lingbot-map?
lingbot-map, with 36,798 lines written; textgen has 29,113.

The proof: Robbyant/lingbot-map's code at commit b9dd1b1

Which has more GitHub stars, textgen or lingbot-map?
textgen, with 47,737 stars; lingbot-map has 18,556.

The proof: oobabooga/textgen on GitHub

Which has more tests, textgen or lingbot-map?
textgen, with 1 test files.

The proof: oobabooga/textgen's code at commit c93f887

Which was updated more recently, textgen or lingbot-map?
lingbot-map: its last push was on October 14, 2026, and textgen's on August 17, 2026.

The proof: Robbyant/lingbot-map's commits on GitHub

See inside your code, today.

Paste your repo and see it drawn, part by part: a medium one in under a minute.

Free, no account.

Or look inside SeeRepo's own →