Tracking issue for "interesting" modules

[hobofan]

This issue aims to collect modules (and module versions) that are "interesting" in some way from the standpoint of the bcr-ui.

This usually involves exhibiting some property that is somehow reflected in the bcr-ui and where we would like to know what modules to look at to see if some functionality/styling is still working as intended.

List

• Has yanked version
  • zlib version 1.2.12 UI link
• Has no maintainer
  • abseil-py UI link
• Has a maintainer with a "long-ish" name (may stress sidebar styling)
  • rules_go UI link
  • rules_python UI link
• Has a long module name
  • com_github_rabbitmq_looking_glass UI link
• Has some non-semver version identifiers
  • rules_xcodeproj, e.g. version 1.0.0rc1 UI link
• Has a lot of dependent modules
  • bazel_skylib UI link
• Has no dependent modules
  • pigz UI link
• Has no dependencies
  • platforms version 0.0.6 and earlier UI link
• Has dependencies with long version identifiers
  • grpc dependencies boringssl and upb UI link
• Uses variables/expressions in the MODULE.bzl file
  • contrib_rules_jvm version 0.18.0 UI link

[alexeagle]

Note, I did a temporary pass at this in #157 but it's not the principled or evergreen solution.