Skip to content

qdrant/qdrant-edge-demo

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

Open on GitHub
Current stars
62
Activity since
2026
Latest activity
Apr 2026

Public star activity

Last 30 days
+1
Last 90 days
+6
Actions / day
0.1
Public star actions

stars from January 13, 2026 to April 8, 2026, peaking at 6.6 STARS3 MO6APR 2026JAN 2026

6 stars on April 8, 2026.

stars by date
Datestars
January 13, 20262
January 18, 20263
January 22, 20264
January 29, 20265
April 8, 20266

The commit history reads qdrant/qdrant-edge-demo 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/qdrant-edge-demo
File change frequency
File change frequency for qdrant/qdrant-edge-demo
Bus factor
Bus factor for qdrant/qdrant-edge-demo
Maintenance pulse
Maintenance pulse for qdrant/qdrant-edge-demo
Contributors
Contributors for qdrant/qdrant-edge-demo
Language activity
Language activity for qdrant/qdrant-edge-demo
Commit activity
Commit activity for qdrant/qdrant-edge-demo
Recent TODO/FIXME movement
Recent TODO/FIXME movement for qdrant/qdrant-edge-demo

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/qdrant-edge-demo.

Notes on qdrant/qdrant-edge-demo

How many stars does qdrant/qdrant-edge-demo have?
GitHub currently reports 62 stars for qdrant/qdrant-edge-demo. 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 qdrant-edge-demo?
gitdebt observed about 6 public star actions for qdrant/qdrant-edge-demo 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.
Is qdrant-edge-demo still active?
Public archive data shows about 1 star actions for qdrant/qdrant-edge-demo in the latest 30 days of coverage. For repository activity, use the commit heatmap, commit trend, and contributor charts on this page.
When was qdrant-edge-demo created?
qdrant/qdrant-edge-demo was created on December 23, 2025. The first public star activity observed for qdrant/qdrant-edge-demo is from Jan 2026.

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/qdrant-edge-demo star history
<a href="https://gitdebt.com/qdrant/qdrant-edge-demo?ref=readme">
  <picture>
    <source media="(prefers-color-scheme: dark)" srcset="https://api.gitdebt.com/api/repos/qdrant/qdrant-edge-demo/chart.svg?theme=dark" />
    <img alt="qdrant/qdrant-edge-demo star history" src="https://api.gitdebt.com/api/repos/qdrant/qdrant-edge-demo/chart.svg?theme=light" />
  </picture>
</a>

<sub>Star history source: Historical star data · Covers through April 8, 2026 · Still updating — <a href="https://gitdebt.com/qdrant/qdrant-edge-demo?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.