Software slogan: „toda la ira del vudú“.

Shotstars allows you to monitor any public repository from a distance. For example, can a web user tell how many stars an interesting Github repository has gained or lost in a month? (IT hosting doesn't provide information on star decrement, even to the owner of their own projects). Shotstars takes care of calculating and visualizing not only this, but much, much more. In addition to statistics, the tool can identify repositories with 𝔽𝕒𝕜𝕖 𝕊𝕥𝕒𝕣𝕤.

Claimed functions:

• Shotstars will help find and expose naked kings and their retinue (fact: stars in some repositories are inflated).
• Shotstars calculates parameters: aggressive marketing, projected growth, fake stars, peak of popularity and its date.
• Shotstars will calculate progress or regression over the last month (median - trend in percentage change and average - calculated in fact in times).
• Shotstars Shotstars will calculate the names of the months that had the most and the least stars (mode / anti-mode), and will also display the entire history of stars by quartiles, a similar calculation is made by year.
• Shotstars will output the longest period of time without adding stars.
• Shotstars scans repositories for stars added and removed with statistics for a selected time period.
• Shotstars reports the real date of the repository (fact: developers can declare/fake/change the date of their projects commits, but Shotstars will not fool them, the utility will display real numbers).
• Shotstars will show ~ the size of any public repository.
• Shotstars will also provide a short description of the repository.
• Shotstars will report the underlying PL of a repository as background in the HTML report.
• Shotstars offers a scan history with a selection of previously registered projects for quick checking.
• Shotstars generates CLI/HTML reports (stats, time periods, duplicate user activity, urls and json).
• Shotstars creates graphs and histograms with night mode support (all star history by date, by month, by year, by hour, by days of the week, cumulative set of stars).
• Shotstars can simulate results, documented hack: a function designed to check the utility's operation (to make sure) on dead/stable repositories without moving stars.
• Shotstars finds users that overlap across Github projects, including those with hidden/private profiles.
• Shotstars calculates to the minute and displays the time when the github rescan restriction is lifted (if token is not used).
• Shotstars is created for people and works out of the box, OS support: Windows7+, GNU/Linux, Android (the user does not need: technical skills; registration/authorization on Github and even the presence of Python).
• Shotstars processes tasks with jet speed and for free (cross-platform open source software, donations are welcome).

$ pip install shotstars
$ shotstars_cli

Ready-made "Shotstars" builds are provided for OS GNU/Linux & Windows & Termux (Python is not required)
Download⬇️Shotstars

In Shotstars the scan history is available, now you no longer need to enter or copy/paste the URL each time, specify the keyword his/history instead of the repository url and select the previously scanned repository by number.

Example presumably of fake stars (this repository was previously caught pirating). From the graph of spikes it is clear that in two weeks the repository gained +5K fake stars (a couple of years later this repository stocked up on fake stars again).

Shotstars also offers a line chart: a cumulative set of stars.

Comparison of two repositories, cumulative set of stars. The upper screenshot is the usual movement of stars, the lower screenshot is the promotion of fake stars.

For any repository, Shotstars will provide all users who have added stars, broken down by date, in json format, which means it's even easier to analyze anomalous peaks on the chart.

Research on the promotion of fake stars / Исследование про накрутку фейковых звезд RU / RU_2 | EN / EN_2

Note that the HTML report is generated when the repository is rescanned. If the user needs to force a specific HTML report, simply enable star simulation. 👇
A documented software hack - or side function designed to test the script on dead/stable repositories without star movement.
To simulate the process, the user must scan the new repository once,
adding it to the database; randomly delete and add any lines to a file
(OS GNU/Linux and Termux):
/home/{user}/.ShotStars/results/{repo}/new.txt
(OS Windows):
C:\Users\{User}\AppData\Local\ShotStars\results\{repo}\new.txt;
run a second scan of the same repository.

There are scanning restrictions from Github 【6K stars/hour from one IP address】.
In Shotstars with a Github token limits are gone and you can scan repositories up to 【500K stars/hour】.
Steps to get a token (free):

1. register for an account on Github (if you don’t already have one);
2. open your profile -> settings -> developer settings -> personal acces tokens -> generate new token;
3. insert the resulting token (string) into in the field instead of 'None'
   GNU/Linux & Android/Termux::
   /home/{user}/.ShotStars/results/config.ini
   OS Windows::
   C:\Users\{User}\AppData\Local\ShotStars\results\config.ini.

The Github token belongs to the user, is stored locally and is not transferred or downloaded anywhere.
You can parse both your own and third-party repositories (by default, registration/authorization/token are not required).

Shotstars позволяет следить со стороны за любым публичным репозиторием. Например, может ли пользователь сети сказать: сколько прибавилось или убавилось звезд у какого-нибудь интересного github-репозитория за месяц? (IT-хостинг не предоставляет информацию по убыванию звезд, даже хозяину своих собственных проектов). Shotstars позаботится вычислит и визуализирует не только это, но и многое, многое другое. Кроме статистики, инструмент позволяет вычислять репозитории с накрученными звездами.

Заявленные функции:

• Shotstars поможет найти и разоблачить голых королей и их свиту (факт: звезды в некоторых репозиториях накручивают).
• Shotstars рассчитывает параметры: агрессивный маркетинг, прогнозируемый рост, фейковые звезды, пик популярности и его дата.
• Shotstars рассчитает прогресс или регресс за последний месяц (медиану — тенденцию в процентном изменении и среднее — рассчитанное по факту в разах).
• Shotstars вычислит имена месяцев, в которых было всех больше и всех меньше получено звезд (мода / анти-мода), а также раскрасит всю историю звезд по квартилям, аналогичный расчет и по годам.
• Shotstars выведет самый протяженный период времени без прибавления звезд (черная полоса).
• Shotstars проверяет репозитории на предмет прибавления и убавления звезд со статистикой за выбранный период времени.
• Shotstars сообщает реальную дату создания репозитория (факт: разработчики могут заявлять/подделывать/изменять дату создания своих проектов и коммитов, но Shotstars им не обмануть, утилита отобразит реальные цифры).
• Shotstars покажет ~ размер любого публичного репозитория.
• Shotstars также предоставит краткое описание репозитория.
• Shotstars сообщит основной ЯП у репозитория в виде фона в HTML-отчете.
• Shotstars предлагает для быстрой проверки историю сканирований с выбором ранее учтенных проектов.
• Shotstars генерирует CLI/HTML отчеты (статистика, периоды времени, дублирующая активность пользователей, url's и json).
• Shotstars создает графики и гистограммы с поддержкой ночного режима (вся история звезд по дате/времени: по месяцам, по годам, по часам, по дням недели, кумулятивный набор звезд).
• Shotstars умеет имитировать результаты, задокументированный хак: функция, призванная проверить работу утилиты (удостовериться) на мертвых/стабильных репозиториях без движения звезд.
• Shotstars находит пересекающихся у Github-проектов пользователей, в т.ч. и тех, у кого профиль скрыт/приватный.
• Shotstars рассчитывает с точностью до минуты и отображает время снятия github-ограничения на повторные сканирования (если не используется token).
• Shotstars создан для людей и работает из коробки, поддержка OS: Windows7+, GNU/Linux, Android (от пользователя не требуются: владения техническими навыками; регистрация/авторизация на Github и даже наличие Python).
• Shotstars отрабатывает задачи с реактивной скоростью и задаром (open source, кроссплатформенность, донаты приветствуются).

Существуют ограничения на сканирование со стороны Github 【6K звезд/час с одного IP адреса】.
В Shotstars с Github-токеном ограничения уходят и можно сканировать репозитории до 【500K звезд/час】.
Шаги для получения токена (бесплатный):

1. зарегистрируйте аккаунт на Github (если у вас его еще нет);
2. откройте профиль -> settings -> developer settings -> personal acces tokens -> generate new token;
3. полученный токен (строку) вставьте в поле заместо 'None' в файл
   OS GNU/Linux & Android/Termux::
   /home/{user}/.ShotStars/results/config.ini
   OS Windows::
   C:\Users\{User}\AppData\Local\ShotStars\results\config.ini.

Github-токен принадлежит пользователю, хранится локально и никуда не передается и не скачивается.
Парсить можно, как свои, так и сторонние репозитории (по умолчанию регистрация/авторизация/токен не требуются).

В Shotstars доступна история сканирований, не нужно теперь каждый раз вводить или копи/пастить url, укажите вместо url репозитория ключевое слово his/history и выберите цифрой ранее сканируемый репозиторий.

Обратите внимание, что HTML-отчет создается при повторном сканировании репозитория. Если пользователю требуется принудительно получить особенный HTML-отчет, просто включите симуляцию звезд.

1. Shotstars for Windows 7.

2. Shotstars HTML-report.

3. Shotstars for Android/Termux.

4. Shotstars Limit Github/API (If you don't use the free token).

5. Shotstars Scan History.

6. Shotstars Discovers Hidden Developer Activity.

Shotstars is awesome, it sees everything. Github says the repository hasn't had any commits in a month, but there has been some subtle activity, like PR updates, etc. (by the way, commit rewriting and date manipulation is also easily detected).

7. Shotstars finds users that overlap across Github projects, including those with hidden/private profiles.

8. Shotstars generates HTML-CLI timelines of a repository's star history, both new and gone.

Comparison of two repositories based on stellar history. It is clear that the peak of popularity of the first repository has long passed, the development has gone into decline (forks). The second repository is a legend and is steadily gaining popularity.

Starry hour. Repository from location RU. It is clear that its audience is European, in the morning hours, at night, much fewer stars come.

Starry day of week. From the graph it is clear that stars come intensively at the beginning and end of the working week for this repository. Oh, and outside the US, people start their workweek according to international norms — on Monday, not Sunday.

9. Clear cache.

• "Date-update (including hidden update)" — The metric displays two things: firstly, if a developer pushes a commit and then completely erases the commits from the server and/or overwrites them, Shotstars will know about it and tell you; secondly, the metric will be updated if, for example, there are no pushes, but a pull request is cancelled/added, etc.

• "Peak-stars-in-date" — The metric displays the date (per day) on which the maximum number of stars was received.

• "The-trend-of-adding-stars (forecasting)" — The metric displays the predicted increase in stars per day based on the repository history and algorithm.

• "Most-of-stars-d.w. / Smallest-of-stars-d.w." — The metric displays the calculation of two days of the week for the entire history of the repository (the most profitable day of the week by stars and the day with the least number of stars, mod/anti-mod).

• "Most-of-stars-month / Smallest-of-stars-month" — The metric displays the calculation of two months in the entire history of the repository (the most profitable month by stars and the month with the least stars, mode / anti-mode).

• "Distribution-of-stars-by-month" — Calculation of stars by month for the entire history of the repository (may include rare phenomenon: private stars, when the sum of all stars ≠ 'GitHub-rating'), coloring of the range of stars by quartiles (green: x > Q3); (yellow: Q1 <= x <= Q3); (red: x < Q1), The font size also decreases from Q3...Q1. Groups are not always arranged "3/6/3", for example, the groups of the "Shotstars" repository are arranged "3/4/5". The characteristic is calculated when the age of the repository is at least one month.

• "Distribution-of-stars-by-year" — Same as the metric '"Distribution-of-stars-by-month"', but the calculation is not by month, but by year, and the metric does not display the number of private stars. The characteristic is calculated when the age of the repository is at least one year.

• "Longest-period-without-add-stars" — The metric displays the longest time span when no stars were submitted to the repository, i.e. every day in a row there were 0 stars (black streak).

• "Median-percentage-change" — The metric reflects the average trend in stars (i.e. does not take into account sharp fluctuations in stars, such as fake stars or a sharp drop/popularity from the media), calculated as a percentage, the ratio of the last month to the penultimate month. Positive numbers are easy to interpret, negative ones are not. The simplest example: a user scans a repository at the beginning of January (in November, the repository received +30 stars, and in December, +60 stars), the metric will display "100%"; if everything was the other way around (in November, the repository received +60 stars, and in December, +30 stars), the metric will display "-50%" (not "-100%"). The characteristic is calculated when the repository is at least two months old.

• "Average-change-in-fact" — Unlike the "Median-percentage-change" metric, it reflects not the average trend, but the real state of affairs, i.e. the arithmetic mean and takes into account all fluctuations and dips in stars for the same period (the ratio of the last month to the penultimate month), but is calculated not in percentages, but in times and units (stars). Example: in November the repository added +30 stars, in December +60 stars, then the metric will display - "2 times (30 stars)" and vice versa, if in November +60 stars, and in December +30 stars, then the metric will display - "-2 times (-30 stars)". The characteristic is calculated when the repository is at least two months old.

• "Aggressive-marketing" — The metric accepts the following values: "—"; "Low"; "Medium"; "High"; "Hard"; "Hard+". "—" means that the repository consistently receives or does not receive stars, without jumps, usually such repositories do not care about their popularity, are rarely/not mentioned in the media. "Low"; "Medium"; "High" — these repositories are repeatedly mentioned in the media, the movement of stars is uneven, they can attract hundreds of stars per day, the popularity of the repositories is high. "Hard" — frequent and frantic, uneven movement of stars, i.e. unnatural, the promotion of fake stars. "Hard+" — usually this is multiple promotion of fake stars in large quantities, i.e. more than once. The characteristic is calculated when the repository is at least two months old.

• "Fake-stars" — The metric takes the following values: "Yes"; "Yes, multiple attempts to promote fake stars"; "—". In the first case, this could be a one-time, but large promotion of fake stars or regular promotion of stars little by little. In the second case, these are obvious and multiple promotions of fake stars. "—" means that Shotstars did not detect fake stars. The characteristic is calculated when the repository is at least two months old.

• "New stars" — New stars for the repository from the penultimate scan to the last scan. The characteristic is calculated based on the frequency of repository scans. For the graph, the actual parsing is calculated, i.e. the stars received for the entire history of the repository.

• "Gone stars" — The metric displays those users: who removed their stars from the repository; or deleted their account from the Github platform; or switched their profile to "private" mode - such a profile, like a deleted one, can lead to "404" by link, i.e. Github (not always) completely hides all user activity and their personal page, but such an account can conduct activity that is almost never displayed anywhere except by the account owner (for example, only reactions are displayed). This metric is not calculated for the entire history of the repository, but starts from the date of the first scan. Gone stars for the repository for the period from the penultimate scan to the last scan. The characteristic is calculated based on the frequency of repository scans.

• "Cross-users" — The metric only displays those overlapping users that overlap in the scanned repositories relative to a specific scanned repository.

Many good softwares have Easter eggs. Shotstars has them too, try looking for something related to the project itself, you'll get...