Skip to the main content
The Repo Vitals mark: a pulse that ends in a commitREPO VITALS

applicable weight 65%

open-education-club-by-yandex/deep-vision-and-graphics-shad

Language: Jupyter Notebook
branch fall25
mirror

Course about deep learning for computer vision and graphics co-developed by YSDA and Skoltech.

Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 65%analysed 17 September 2026 at 21:39 UTC — part unavailable

What the 100 is made of

category weight
Documentation 20Activity 20Security 20CI/CD 15Issues 15Code health 10

The light segments — Security: will appear with a member token; Issues: the tracker is empty or not set up. The rest share their weight for now.

Six categories

earned / weight
Documentation and best practicessignal coverage 61%
10.5–22.5 / 30.8
partial
Project activity
20.8 / 30.8
scored
Securitywill appear with a member token
no data
CI/CDsignal coverage 50%
0–11.5 / 23.1
partial
Issuesthe tracker is empty or not set up
no data
Code health
0–15.4 / 15.4
collection failed
States:
scored
partial
no data
weight goes to the rest
collection failed
interval, not zero
Not measured: CI runs
closed by the platform
will become a group once access opens
Not measured: tests directory, docs directory, Dockerfile, contributing guide, TODO/FIXME density
couldn't see it
the platform's window was truncated: a deep file or a recent version may have fallen outside it

Strengths

what's already done
  • Contributions are spread across authors
  • A team works on the project (6 authors)
  • Work goes on without long pauses (7 weeks)
  • Commits span the whole year (21 commits)
  • The license file is in place

What affected the score

Penalties

Documentation and best practices

  • −4
    README2,486 chars, no quickstart
  • −3
    dependency lockfilemissing
  • −1
    share of short commit messages — 44%

Project activity

  • −5
    last releaseno releases or version tags
  • −4
    last commit — 305 days
  • −<1
    commits in the last year — 21 commits
  • −<1
    weekly activity — 7 weeks

CI/CD

  • −12
    SourceCraft CI configurationmissing

Not measured — interval width

Not a penalty: the lower bound of the score counts the metric as zero, the upper bound as full

Documentation and best practices

  • up to −3
    tests directorydata not collected
  • up to −3
    docs directorydata not collected
  • up to −3
    Dockerfiledata not collected
  • up to −2
    contributing guidedata not collected

CI/CD

  • up to −12
    CI runsdata not collected

Code health

  • up to −15
    TODO/FIXME densitydata not collected

What will raise the score

by strength of impact
  • CI/CD
    +12
    add a SourceCraft CI configuration (.sourcecraft/ci.yaml); the service does not see external CISourceCraft CI configurationwhy: the build and the checks are reproducible for whoever takes the code
  • Activity
    +5
    publish a release or tag a versionlast releasewhy: the build and the checks are reproducible for whoever takes the code
  • Activity
    +4
    make a commit soonlast commit — 305 dayswhy: the repository shows it is alive, not abandoned
  • add a quickstart section to the README+4
  • add a dependency lockfile+3
  • write meaningful commit messages+1
  • commit more often+<1
  • spread work across more weeks instead of bursts+<1