moturus/motor-os
Grade a repo

0

/ 100

GradeB

Good community traction and solid fundamentals. Nearly in the top tier.

A simple, fast, and secure operating system for the cloud.

Documentation73
Engineering77
Health100
Rust1,085Apache-2.0today

Documentation

73

Contributing guide5pt52

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.

README12pt55

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

77

Issue and PR templates6pt0

No issue or PR templates found (−100 pts).

→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.

Reproducibility6pt70

Lockfile present (src/bin/httpd/Cargo.lock). Installs are reproducible.

Tests18pt80

Test files detected (src/bin/russhd/tests).

CI/CD14pt100

CI is configured (src/third_party/zero/.travis.yml).

Linting and formatting5pt100

Linter or formatter configured (src/third_party/memchr/rustfmt.toml).

Project health

100

Dependency manifest6pt100

Dependency manifest found (src/bin/httpd-axum/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)
  • 34
    Forks
  • 0
    Releases

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 1,085
    Watchers

Responsiveness

  • 1d 15h
    Median issue response
  • 14h
    Median PR merge time
  • 8
    Open issues
Repository files10 root entries
  • docs
  • img_files
  • src
    Good: Licensed under Apache-2.0.
    Good: Code of conduct present.
    Good: Test files detected (src/bin/russhd/tests).
    Good: CI is configured (src/third_party/zero/.travis.yml).
    Good: Linter or formatter configured (src/third_party/memchr/rustfmt.toml).
    Good: Lockfile present (src/bin/httpd/Cargo.lock). Installs are reproducible.
    Good: Security policy present.
    Good: Dependency manifest found (src/bin/httpd-axum/Cargo.toml).
  • .gitignore
    Good: .gitignore present.
  • CHANGELOG.md
  • 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-APACHE
  • LICENSE-MIT
  • Makefile
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
    Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    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.