UCL / UCL/open-source

List of weird plots/elements in our test 8Knot/Augur deployment.

Open
#26 4 comments 0 reactions 3 assignees View on GitHub

@razekmh is already working on this.

Since Oct 15, 2025.

bug core
Dominant language
HTML
Stars
9
Forks
8
Avg merge
3d 13h
Merged PRs (30d)
4

Description

Weird plots

  1. Repo Overview/Package Version Updates - appears to be 96% up-to-date across our 40 test repos.
    • c.f. eightknot.osci.io (looks reasonable)
    • Could be related to unfound dependencies? Problems with the libyear cli.
    • Data in the augur.repo_deps_libyear seems to only have 14 repos (only python? can't use R?) and the data is largely consistent with the plot.
  2. Repo Overview/OSSF Scorecard - Original 15 and some of the second batch are there. Not all of the new repos have the scorecard even after 24 hrs running.
  3. Contibutor Types/Lottery Factor Pie charts at 100% none (only for commits! other actions look reasonable)
    • c.f. eightknot.osci.io which looks reasonable.
  4. Contributor Types/Lotter Factor - line chart consistently strange as with the pie charts. At 1 for commits.
    • Could be some of the contributor IDs in the augur.commits table being NULL. Even with GitHub accounts associated (Haroon's). To investigate.
  5. Affiliation/Unique contributor email domains - basically empty: 100% "Other". But the chart weighted by commits is reasonable.
  6. All remaining Affiliation plots look off. Probably the same underlying reason as 5.
  7. CHAOSS/Lottery Factor - Commits again wrong (other actions look reasonable)
    • What is the difference between this and the plots in contributor types?
  8. CHAOSS/Project Velocity - Only 15 repos, where are the remaining 25?

Definition of done

  • All weird plots are either understood or deemed not important for our needs.
  • Opened any genuine bugs on upstream.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.