yselivonchyk/pytorch
Grade a repo

0

/ 100

GradeB

Polished work that hasn't found its audience yet.

Top 22% of 5,156 graded repos

Tensors and Dynamic neural networks in Python with strong GPU acceleration

Documentation97
Engineering82
Health75
C++0Other5y ago

Top fixes

Highest-impact changes first, ranked by point weight

8 to address
  1. 1
    Tests18pt

    Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.

  2. 2
    CI/CD14pt

    Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.

  3. 3
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

  4. 4
    CI/CD14pt

    Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.

Working through the fixes? Let every push regrade itself.

The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

97

Install and run instructions9pt90

README documents how to install the project.

Contributing guide5pt97

Contributing guide is detailed and thorough.

README12pt100

README is present.

License6pt100

Licensed under Other.

Engineering

82

CI/CD14pt72

CI is configured (.github/workflows/build_linux_binaries.yml).

Tests18pt80

Test files detected (android/pytorch_android/src/androidTest/java/org/pytorch/PytorchHostTests.java).

Reproducibility6pt80

Lockfile present (requirements.txt). Installs are reproducible.

Linting and formatting5pt100

Linter or formatter configured (.flake8).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

75

Activity5pt5

No pushes in over 2 years. Looks unmaintained (−95 pts).

→ A recent commit signals the project is alive and worth using.

Dependency manifest6pt100

Dependency manifest found (requirements.txt).

Repository metadata5pt100

Repository has a description.

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • -
    Commits (30d / 90d)
  • 0
    Forks
  • 0
    Releases

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 0
    Watchers

Responsiveness

  • -
    Median issue response
  • -
    Median PR merge time
  • 0
    Open issues
Repository files55 root entries
  • .circleci
    Good: Environment pinned via .circleci/docker/centos-rocm/Dockerfile.
    Good: .gitignore present.
  • .ctags.d
  • .github
    Good: CI is configured (.github/workflows/build_linux_binaries.yml).
    Good: Issue or PR templates present.
  • .jenkins
  • android
    Good: Test files detected (android/pytorch_android/src/androidTest/java/org/pytorch/PytorchHostTests.java).
  • aten
  • benchmarks
  • binaries
  • c10
  • caffe2
  • cmake
  • docker
  • docs
  • ios
  • modules
  • scripts
  • submodules
  • test
  • third_party
  • tools
  • torch
  • .bazelrc
  • .bazelversion
  • .clang-format
  • .clang-tidy
  • .cmakelintrc
  • .dockerignore
  • .flake8
    Good: Linter or formatter configured (.flake8).
  • .gitattributes
  • .gitignore
  • .gitmodules
  • .nojekyll
  • aten.bzl
  • BUILD.bazel
  • CITATION
  • CMakeLists.txt
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • codecov.yml
  • CODEOWNERS
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • docker.Makefile
  • Dockerfile
  • GLOSSARY.md
  • LICENSE
    Good: Licensed under Other.
  • Makefile
  • mypy-strict.ini
  • mypy.ini
  • NOTICE
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Good: README has code examples.
    Good: README links to a live demo or deployed app.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • requirements-flake8.txt
  • requirements.txt
    Good: Lockfile present (requirements.txt). Installs are reproducible.
    Good: Dependency manifest found (requirements.txt).
  • setup.py
  • ubsan.supp
  • version.txt
  • WORKSPACE
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/yselivonchyk/pytorch)](https://www.repo-grade.com/report/yselivonchyk/pytorch)

More graded C++ repos