liteparse

LlamaIndex lightweight parser for document extraction.

A single Bluesky mention ranks #1 in a near-empty Bluesky pool (3 total items), producing a single-source artifact. No GitHub, HN, X, Reddit, or Product Hunt signals exist. The entity is a real LlamaIndex utility but has no organic developer traction.

Why now: Bluesky pool is severely undersampled (3 items vs 1000 HF rows), causing rank distortion that the composite algorithm amplified.

• Only Bluesky signal with rank=1, but Bluesky pool has only 3 items total (sourceStats.bs.count=3)
• No GitHub, Hacker News, X/Twitter, Reddit, or Product Hunt presence despite weights summing to 0.92 for those sources
• 175 of 200 pool items are single_source — this is systemic noise pattern, not exception
• HF model space has 1000 rows but zero signal for this entity there

Considerations: Bluesky rank #1 is mathematically inevitable in a 3-item pool, not organic popularity. The run-llama namespace provides false credibility — being in a known org doesn't mean this specific repo matters. No commit velocity, release activity, or issue discussion is visible.

EMERGING SIGNAL · Ignore: Do not track; if monitoring LlamaIndex ecosystem, watch their main repos (llama-index, llama-parse) instead.

Sources: Bluesky search: run-llama/liteparse