envmodules/modules
Grade a repo

0

/ 100

GradeB

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

Environment Modules: provides dynamic modification of a user's environment

Documentation82
Engineering74
Health100
Tcl851GPL-2.0today

Documentation

82

README12pt70

README is present.

Contributing guide5pt72

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under GPL-2.0.

Engineering

74

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.

Reproducibility6pt70

Lockfile present (doc/source/requirements.txt). Installs are reproducible.

Tests18pt80

Test files detected (testsuite/modulefiles.2/modemptyarg/test).

CI/CD14pt85

CI is configured (.github/workflows/lint_tests.yaml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (doc/source/requirements.txt).

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)
  • 121
    Forks
  • 38
    Releaseslatest 7y ago

Community

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

Responsiveness

  • 48d 3h
    Median issue response
  • 1d 8h
    Median PR merge time
  • 37
    Open issues
Repository files31 root entries
  • .github
    Good: CI is configured (.github/workflows/lint_tests.yaml).
    Good: Issue or PR templates present.
  • doc
    Good: Lockfile present (doc/source/requirements.txt). Installs are reproducible.
    Good: Dependency manifest found (doc/source/requirements.txt).
  • init
  • lib
  • script
  • share
  • tcl
  • testsuite
    Good: Test files detected (testsuite/modulefiles.2/modemptyarg/test).
  • .codespellrc
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .globalrc
  • .hunspell.en.dic
  • .readthedocs.yaml
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • codecov.yml
  • configure
  • CONTRIBUTING.rst
    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.
    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).
    Good: Contributing guide describes the PR/review workflow.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • COPYING.GPLv2
  • GOVERNANCE.rst
  • INSTALL-win.rst
  • INSTALL.rst
  • Makefile
  • Makefile.inc.in
  • MIGRATING.rst
  • NEWS.rst
  • README.md
    Good: README is present.
    Issue: README has little structure (−15 pts). Add 2-3 headings for +8 pts; 4+ earns +15 pts.Fix: Break it into sections (Overview, Install, Usage, Contributing) using Markdown headings.
    Good: README includes screenshots or visuals. Great for first impressions.
    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.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • SECURITY.md
    Good: Security policy present.
  • site.exp.in
  • siteconfig.tcl
  • version.inc.in