This repository has been archived by the owner on Oct 12, 2020. It is now read-only.
Add mode to scan first stargazers #19
Merged
Conversation
This file contains 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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Goal of this PR
Fixes #18
This PR introduces a new option to scan the first X stargazers of a repository. This is useful when a repository virtually boosted its popularity by botting/buying stargazers at its infancy but stopped once natural growth was able to sustain itself.
It also improves the error handling with the different user inputs for the
--starsoption.Here is an example of scanning the same repository with global stats and then with the first 2000 stars it got:
As you can see, the organic growth was so high that on average values, the initial boost is completely undetectable. This new option makes it possible to detect it.