ue4ss-re/re-ue4ss
Grade a repo

0

/ 100

GradeD

Strong community interest, but tests, CI, or docs need work.

Top 50% of 5,156 graded repos

Injectable LUA scripting system, SDK generator, live property editor and other dumping utilities for UE4/5 games

Documentation90
Engineering37
Health100
C++2,611MIT1mo ago

A low grade is a to-do list, not a judgment of your code

Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to A (91).

See your top fixes
Now
D
66
Potential
A
91

Top fixes

Highest-impact changes first, ranked by point weight

13 to address
  1. 1
    Tests18pt

    Add automated tests. They prove the code works and give contributors confidence to make changes.

  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 a lint step to catch style issues automatically.

  4. 4
    CI/CD14pt

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

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

90

Contributing guide5pt80

Contributing guide is detailed and thorough.

README12pt90

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

37

Tests18pt0

No tests detected anywhere in the repository.

→ Add automated tests. They prove the code works and give contributors confidence to make changes.

Linting and formatting5pt0

No linter or formatter config found.

→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.

CI/CD14pt57

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

Reproducibility6pt70

Lockfile present (deps/first/patternsleuth_bind/Cargo.lock). Installs are reproducible.

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (deps/first/patternsleuth_bind/Cargo.toml).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • -
    Commits (30d / 90d)
  • 429
    Forks
  • 15
    Releaseslatest 3y ago

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 2,611
    Watchers

Responsiveness

  • 5h
    Median issue response
  • 4h
    Median PR merge time
  • 230
    Open issues
Repository files22 root entries
  • .github
    Good: CI is configured (.github/workflows/cmake_build_ue4ss.yml).
    Good: Issue or PR templates present.
  • assets
  • cmake
  • cppmods
  • deps
    Good: Lockfile present (deps/first/patternsleuth_bind/Cargo.lock). Installs are reproducible.
    Good: Dependency manifest found (deps/first/patternsleuth_bind/Cargo.toml).
  • docs
    Good: Contributing guide is detailed and thorough.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Good: Contributing guide describes code style expectations.
    Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • docs-export
  • docs-repo-template
  • tools
  • UE4SS
  • UVTD
  • .clang-format
  • .git-blame-ignore-revs
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • CMakeLists.txt
  • CNAME
  • LICENSE
    Good: Licensed under MIT.
  • 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.
    Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • UE4SS.natvis
  • xmake.lua
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/ue4ss-re/re-ue4ss)](https://www.repo-grade.com/report/ue4ss-re/re-ue4ss)

More graded C++ repos