Skip to content

qdrant/contexto

Star momentum, maintenance concentration, contributor health, and codebase change — one report built from public repository data.

Open on GitHub
Current stars
10
Activity since
2022
Latest activity
Nov 2025

Public star activity

Last 30 days
+1
Last 90 days
+2
Actions / day
0.0
Public star actions

stars from December 8, 2022 to November 4, 2025, peaking at 9.9 STARS2 YR 11 MO9NOV 2025DEC 2022

9 stars on November 4, 2025.

stars by date
Datestars
December 8, 20221
January 10, 20232
September 6, 20233
January 2, 20244
November 19, 20245
December 15, 20246
January 23, 20257
September 26, 20258
November 4, 20259

The last 90 days run ahead of this repository's lifetime average.

The commit history reads qdrant/contexto a second time

methodology

Fix-labelled changes, file change frequency, ownership concentration and maintenance cadence, each computed from this repository's analyzed commit window. None of them is derived from stars, which is why they are allowed to disagree with the curve above.

Fix-labelled changes
Fix-labelled changes for qdrant/contexto
File change frequency
File change frequency for qdrant/contexto
Bus factor
Bus factor for qdrant/contexto
Maintenance pulse
Maintenance pulse for qdrant/contexto
Contributors
Contributors for qdrant/contexto
Language activity
Language activity for qdrant/contexto
Commit activity
Commit activity for qdrant/contexto
Recent TODO/FIXME movement
Recent TODO/FIXME movement for qdrant/contexto

Attention is not adoption.

Stars against usage

No published package was detected for this repository, so there is nothing to lay over star growth.

Earned badges

badge studio

Maintenance, ownership and star-momentum signals, computed from the same commit and star history and embeddable as static images.

Reading badge evidence for qdrant/contexto.

Notes on qdrant/contexto

How many stars does qdrant/contexto have?
GitHub currently reports 10 stars for qdrant/contexto. The chart itself is rebuilt from historical star data, which records star actions and not unstars, so it reads as an attention signal rather than a net star count.
What does recent star activity look like for contexto?
gitdebt observed about 2 public star actions for qdrant/contexto over the latest 90 days of archive coverage (about 1 in the latest 30). This is an approximate attention signal, not a net-star count, because unstars are not present. That's faster than its lifetime average activity pace.
Is contexto still active?
Public archive data shows about 1 star actions for qdrant/contexto in the latest 30 days of coverage. For repository activity, use the commit heatmap, commit trend, and contributor charts on this page.
When was contexto created?
qdrant/contexto was created on December 8, 2022. The first public star activity observed for qdrant/contexto is from Dec 2022.

Put this drawing in your README

markdown for agents

The block below publishes the chart with its source and coverage date stated beside it — the same three facts the title block above shows, as text a reader can check. The prompt underneath hands a coding agent the badges and repo-health charts as well.

README.md · qdrant/contexto star history
<a href="https://gitdebt.com/qdrant/contexto?ref=readme">
  <picture>
    <source media="(prefers-color-scheme: dark)" srcset="https://api.gitdebt.com/api/repos/qdrant/contexto/chart.svg?theme=dark" />
    <img alt="qdrant/contexto star history" src="https://api.gitdebt.com/api/repos/qdrant/contexto/chart.svg?theme=light" />
  </picture>
</a>

<sub>Star history source: Historical star data · Covers through November 4, 2025 · Still updating — <a href="https://gitdebt.com/qdrant/contexto?ref=readme">gitdebt</a></sub>

Light and dark variants, alt text, and one provenance line. Provenance is text in your README, never baked into the image URL, so the chart stays cacheable.

Paste it into Claude Code, Cursor, Codex, or any coding agent with your checkout open. It carries the measured numbers, the exact snippets, and the rules — including replacing an existing star-history widget in place rather than stacking a second chart under it.