rive-app/rive-unity

0

/ 100

Documentation89
Engineering63
Health100
C#204MIT1d ago
Grade a repo

Good shape overall. A few tweaks would push it into the top tier.

Unity runtime for Rive

Documentation

89

Contributing guide5pt47

CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.

→ Add setup instructions, code style notes, and how to run tests.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under MIT.

Engineering

63

Reproducibility6pt0

No dependency lockfile found (−70 pts).

→ Enable and commit packages.lock.json so NuGet restores are repeatable.

CI/CD14pt40

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

Tests18pt80

Test files detected (tests).

Linting and formatting5pt100

Linter or formatter configured (package/Editor/.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (package/package.json).

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)
  • 20
    Forks
  • 16
    Releaseslatest 1y ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 204
    Watchers

Responsiveness

  • 1d 8h
    Median issue response
  • 1d 22h
    Median PR merge time
  • 30
    Open issues
Repository files10 root entries
  • .github
    Good: CI is configured (.github/workflows/add_to_project.yml).
    Good: Issue or PR templates present.
  • examples
    Good: .gitignore present.
  • package
    Good: Linter or formatter configured (package/Editor/.editorconfig).
    Good: Dependency manifest found (package/package.json).
  • tests
    Good: Test files detected (tests).
  • .rive_head
  • CONTRIBUTING.md
    Issue: CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    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).
    Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • 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.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • rive_unity_webgl_patch.diff
  • WEBGL.md