Stargazers history for volcengine/OpenViking is undercounted

Hi OSSInsight team,
We noticed a discrepancy in the star count for the repository volcengine/OpenViking between OSSInsight and GitHub.

What we see

• On OSSInsight (repo page + Public API stargazers/history ), the cumulative stargazers count is around 4,8xx .

• On GitHub, the repository stargazers_count is around 22,9xx (currently ~23k).

Repro steps

1. Call OSSInsight Public API:
2. Observe that the last data point is ~4,799 stargazers (e.g., 2026-04-23: 4799 ).
3. Compare with GitHub REST API:
   • stargazers_count returns ~22,968 (varies slightly day to day).

Cause we use OSSInsight trends data for reporting. This undercount makes the “Stars (cumulative)” metric misleading and affects downstream dashboards/analysis.

Additional context

• The mismatch is persistent across days (not just a single-day lag).

Could you please check whether this repo’s star events are missing from your dataset or whether the ETL/backfill for volcengine/OpenViking is incomplete, and advise on any workaround/timeline?

Thank you.

Wish you all the best

Reproduce the discrepancy between the OSSInsight Public API stargazers/history result for volcengine/OpenViking and GitHub’s stargazers_count. Trace the stargazer event ingestion and ETL or backfill path for this repository; done means the cumulative history reflects the repository’s GitHub star count and downstream metrics are no longer undercounted.