moganlab/mogan

0

/ 100

Documentation86
Engineering58
Health68
Scheme564GPL-3.01d ago
Grade a repo

Popular for its size, but the engineering basics lag behind the interest.

Mogan STEM Suite (based on GNU TeXmacs): Enjoy exploring science and technology!

Documentation

86

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.

README12pt90

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under GPL-3.0.

Engineering

58

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.

Reproducibility6pt0

No dependency lockfile found (−70 pts).

→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.

CI/CD14pt57

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

Tests18pt80

Test files detected (3rdparty/lolly/tests).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

68

Dependency manifest6pt0

No dependency manifest detected at root.

→ Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.

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)
  • 101
    Forks
  • 70
    Releaseslatest 2y ago

Community

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

Responsiveness

  • 4d 21h
    Median issue response
  • <1h
    Median PR merge time
  • 405
    Open issues
Repository files30 root entries
  • .claude
  • .github
    Good: CI is configured (.github/workflows/ci_bump_version.yml).
  • .workflow
  • 3rdparty
    Good: Licensed under GPL-3.0.
    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.
    Good: Code of conduct present.
    Good: Test files detected (3rdparty/lolly/tests).
    Good: Issue or PR templates present.
  • bin
  • devel
  • GSoC
  • hooks
  • misc
  • moebius
  • OSPP
  • packages
  • public
  • src
  • tests
  • TeXmacs
  • tools
  • xmake
  • .clang-format
  • .codex
  • .gitignore
    Good: .gitignore present.
  • CLAUDE.md
  • CONTRIBUTING.md
  • COPYING
  • gfexclude.json
  • gfproject.json
  • LICENSE
  • README_ZH.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.
  • README.md
  • xmake.lua