day8/re-frame2

0

/ 100

Documentation93
Engineering72
Health100
Clojure28MIT1d ago
Grade a repo

Strong early engineering with some momentum.

https://day8.github.io/re-frame2/

Documentation

93

README12pt90

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Contributing guide5pt100

Contributing guide is detailed and thorough.

Engineering

72

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 (requirements.txt). Installs are reproducible.

Tests18pt80

Test files detected (docs/tools/playground/test).

CI/CD14pt85

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

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Project health

100

Dependency manifest6pt100

Dependency manifest found (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)
  • 0
    Forks
  • 0
    Releases

Community

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

Responsiveness

  • —
    Median issue response
  • <1h
    Median PR merge time
  • 1
    Open issues
Repository files31 root entries
  • .beads
    Good: .gitignore present.
  • .claude
  • .clj-kondo
  • .github
    Good: CI is configured (.github/workflows/lint.yml).
  • ai
  • docs
    Good: Test files detected (docs/tools/playground/test).
  • examples
  • implementation
    Good: Licensed under MIT.
  • migration
  • scripts
  • skills
  • spec
  • testbeds
  • tools
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .gitattributes
  • .gitignore
  • .splint.edn
  • AGENTS.md
  • CHANGELOG.md
  • CLAUDE.md
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    Good: Contributing guide describes code style expectations.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • license.txt
  • mkdocs_hooks.py
  • mkdocs.yml
  • 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.
  • requirements.txt
    Good: Lockfile present (requirements.txt). Installs are reproducible.
    Good: Dependency manifest found (requirements.txt).
  • SECURITY.md
    Good: Security policy present.
  • SKILL-REDIRECT.md
  • TESTING.md
  • VERSION