Activity, over time
Daily observations from the public event archive.
Attention
Daily stars & forks
Star accumulation
Cumulative stars
Pull requests
Daily opens & merges
Conversations
Daily issues & comments
Community
Daily accounts & reviews
Releases
Daily releases
Trending history
Daily top 10 · last 90 days · UTC
Mentions
Stars
Forks
Contributors
Latest stargazers
The last 10 distinct accounts we observed this year.
Most active participants
PR, issue, comment & review events in the past year.
Packages
| Package | Version | Downloads · 30d | Trend · 30d |
|---|---|---|---|
liteparsev2.17.0 | v2.17.0 | — | — |
| — | — | — | |
liteparse-pdfiumv1.13.0 | v1.13.0 | — | — |
liteparse-pdfium-sysv1.13.0 | v1.13.0 | — | — |
| — | — | — | |
| — | — | — | |
@llamaindex/liteparsev2.9.0 | v2.9.0 | ≥329.3K | |
| v2.9.0 | ≥34.9K | ||
| — | — | — | |
| — | — | — | |
liteparsev2.17.0 | v2.17.0 | ≥490.7K | |
| — | — | — | |
| — | — | — | |
| — | — | — |
Live mentions badge
Show how many posts mention your project in the last 30 days.
Live mentions · last 30 days
Mentions
Everyone says: PDF parsing is a solved problem. Reality: Most parsers choke on tables and mixed layouts. liteparse uses vision to preserve structure. It’s not just text extraction; it’s layout-aware. run-llama/liteparse
Found a bug in LiteParse 👀 Node.js & Python silently turn invalid ""yaml"" output into JSON instead of throwing an error. Issue #452 👇 liteparse#452 #OpenSource #BugHunting