Skip to content
Snippets Groups Projects
Select Git revision
  • renovate/major-opa
  • advisory/tj
  • main default protected
  • defect/telem
  • docs/pattern
  • spike/go-tools-124-gql
  • spike/go-tools-124
  • chore/deepmap
  • docs/mas
  • build/notify
  • fix/du
  • defect/diff
  • defect/json
  • chore/schema
  • feat/diff-json
  • chore/typo
  • build/binaries
  • build/changelog-
  • defect/otel
  • chore/otel
  • v0.116.2 protected
  • v0.116.1 protected
  • v0.116.0 protected
  • v0.115.3 protected
  • v0.115.2 protected
  • v0.115.1 protected
  • v0.115.0 protected
  • v0.114.0 protected
  • v0.113.5 protected
  • v0.113.4 protected
  • v0.113.3 protected
  • v0.113.2 protected
  • v0.113.1 protected
  • v0.113.0 protected
  • v0.112.0 protected
  • v0.111.1 protected
  • v0.111.0 protected
  • v0.110.2 protected
  • v0.110.1 protected
  • v0.110.0 protected
40 results

internal

  • Clone with SSH
  • Clone with HTTPS
  • Jamie Tanna's avatar
    Jamie Tanna authored
    A slightly more meaningful number than number/percentage of dependencies
    using the given dependency is how many repos are dependent on it.
    
    This provides a more actionable signal that the dependency is important
    if a high number of repositories in the organisation use it, as well as
    allowing a better indication when using several ecosystems, some of
    which use fewer dependencies, and some using 5-10x more, which reduces
    the impact that a given dependency could show as.
    
    As this is a bit more of an interesting signal, we can use this for the
    sorting, too.
    
    Closes #493.
    ff0fb719
    History
    Code owners
    Assign users and groups as approvers for specific file changes. Learn more.
    Name Last commit Last update
    ..