Remove repo clone count from homepage - #836
Merged
Merged
Conversation
amavashev
marked this pull request as ready for review
July 28, 2026 18:31
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Why
Raw repository clone counts include repeat, CI, and bot traffic, so presenting the cumulative number as homepage social proof can undermine credibility with technical evaluators. The data loader already excludes clones from the defensible package-install total, but the homepage still rendered clones as a separate statistic.
Impact
Visitors now see only the package-install count. Internal clone statistics and workflows remain unchanged.
Validation
npm test— 93 tests passednpm run build:fast— site build passednpm run pdfs— all 9 eligible PDFs generated