millenniumdawn/millennium-dawn

0

/ 100

Documentation91
Engineering55
Health100
Python69CC-BY-SA-4.01d ago
Grade a repo

Solid foundation. Invest in docs and CI to grow from here.

Millennium Dawn and it's codebase.

Documentation

91

Contributing guide5pt84

Contributing guide is detailed and thorough.

README12pt90

This repository is large enough that GitHub truncated the file tree. The scan is based on a partial file list, so some checks may under-report.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under CC-BY-SA-4.0.

Engineering

55

Tests18pt0

No tests detected anywhere in the repository.

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

CI/CD14pt72

CI is configured (.github/workflows/auto-label.yml).

Linting and formatting5pt100

Linter or formatter configured (docs/.prettierrc.mjs).

Reproducibility6pt100

Lockfile present (bun.lock). Installs are reproducible.

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (docs/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)
  • 50
    Forks
  • 19
    Releaseslatest 6mo ago

Community

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

Responsiveness

  • 21d 19h
    Median issue response
  • 4h
    Median PR merge time
  • 276
    Open issues
Repository files25 root entries
  • .claude
  • .github
    Good: CI is configured (.github/workflows/auto-label.yml).
    Good: Dependabot covers 3 ecosystems (github-actions, pip, bun). Dependencies stay current.
    Good: Issue or PR templates present.
  • .opencode
  • .vscode
  • common
  • descriptions
  • docs
    Good: Linter or formatter configured (docs/.prettierrc.mjs).
    Good: Environment pinned via docs/.nvmrc.
    Good: Dependency manifest found (docs/package.json).
  • events
  • gfx
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .pre-commit-config.yaml
  • .secrets.baseline
  • AGENTS.md
  • bun.lock
    Good: Lockfile present (bun.lock). Installs are reproducible.
  • Changelog.txt
  • CLAUDE.md
  • CODEOWNERS
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    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.
    Good: Contributing guide includes code examples.
  • descriptor.mod
  • docs-audit.md
  • LICENSE
    Good: Licensed under CC-BY-SA-4.0.
  • Millennium_Dawn.mod
  • 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.
  • SECURITY.md
    Good: Security policy present.