Skip to content

Guide to Activity Tab

Jump to bottom
Jeremy Asuncion edited this page Sep 11, 2023 · 47 revisions

Overview

The activity tab shows installation and maintenance statistics for a particular plugin, including:

  • How many times the plugin has been installed since it was released
  • How many times the plugin has been installed in the past 30 days
  • Installs of the plugin in the past year are graphed
  • How many commits since released, since created, time of last commit, and number of monthly commits in the past year

Topics Include:

Installs

We aim to represent plugin installations from plugin users, excluding those done by plugin developers or for non-user purposes, but there are many caveats. For example, since the installation data we utilize is anonymous, we may show multiple installs from a single user.

We use the Linehaul project to gather install data, which is the same tool used by PyPI. Linehaul shows all installs, including developer installs used for troubleshooting or building the package. The developer installs can fall into multiple buckets including continuous integration (CI), mirror installs, and release candidate installs. PyPI shows all installs. You can view install data from PyPI at pypistats.org.

We select for installs made by plugin users and exclude as many developer installs as possible. We clean the install data from Linehaul by excluding CI installs such as those from AWS (Amazon Web Services), mirror installs, and release candidate installs. Our data may not match pypi stats due to this data exclusion. (e.g. napari-allencell-segmenter on the hub vs napari-allencell-segmenter on pypi).

Data Graphs of Installs

  • We show the past 12 completed months from the previous month to the current month. So if it’s January 2023, we show February 2022 through January 2023 as in this example:

    9208-installs-napari-skimage-regionprops

  • The dashed line indicating “Public release” aligns with the month it was publicly released, as shown in this example:

    78-installs-vollseg-napari-mtrack

  • The data for the first month of the plugin’s public existence may not be for a complete month if the plugin was released at any date after the first of the month. We still show what data we had for that month in aggregate once that month is complete and we are in the next month. In this example, the plugin was released more than one month ago but not two months ago. It shows 1 install in the past 30 days, which may not be all the installs for the current month.

    2-installs-wsi-reader

  • Graphs are not displayed if a plugin was released in the current month.

    5-installs

Terminology used to describe installs

  • If a plugin was publicly released < 7 days ago, we say “less than a week ago”.
  • If a plugin was publicly released >= 7 days, but < 14 days prior, we say "a week ago".
  • If a plugin was publicly released >= 14 days, but < 30 days prior, we say "n weeks ago". e.g., “3 weeks ago”
  • If a plugin was publicly released >= 30 days, but < 24 months prior, we say "n months ago". e.g., “7 months ago” or “19 months ago”
  • If a plugin was publicly released > 24 months prior, we say "n years ago". e.g., "2 years ago" or “6 years ago”

Maintenance

If a plugin is on GitHub, the following maintenance statistics are shown:

  • Commits since released
  • Commits since plugin repo was created
  • Time of the latest commit
  • Monthly commits in past year are graphed

Here is an example:

Maintenance-napari-compressed-labels-io

The statistics for plugins on GitHub are gathered using the GitHub API. For more information on GitHub statistics, refer to Repository statistics. Note that the graph refers to statistics from the date the repository was created. The statistics may be inaccurate if a repository is renamed or if it is transferred from one user account to another.

We do not track statistics for plugins on other platforms.

Clone this wiki locally