Presenting stars and forks

[abstractionfactory]

The API now has information on stars and forks in the provider index (not the version) in the following format. Note that the repository information is (incorrectly) present on the version, not on the provider index file.

{
  "popularity": 5, /* Number of stars */
  "fork_count": 2, /* Number of forks from this repository */
  "fork_of_link": "https://github.com/hashicorp/aws", /* Link to the upstream repository this provider was forked from */
  "fork_of": "hashicorp/aws", /* OpenTofu name for the provider if it can be identified based on the upstream repository, may not be present */
  "upstream_popularity": 36,
  "upstream_fork_count": 16
}

We now have to decide how to present this in the frontend, which is where input is needed. We could, for example, do something like this:

[GITHUBICON]   opentofu/aws
[UPSTREAMICON] hashicorp/aws
[STARICON]     5 ([UPSTREAMICON] 36)
[FORKICON]     2 ([UPSTREAMICON] 16)

The fork icon could be something along these lines:

  O <-
  |
 / \
|   |
O   O

Your input is highly valued, please comment below!

[ImIOImI]

I don't have anything to add other than I think this is an intuitive way to present interesting information. The only other thing that would be helpful is to measure how up to date the fork is (how many commits ahead and behind it is, etc.)... but I assume the API doesn't return that.

[abstractionfactory]

@ImIOImI the main issue here is the reindexing frequency. We only reindex if we have a new version, otherwise we don't touch the data at all.