dbmcclain/lisp-actors

0

/ 100

Documentation60
Engineering29
Health68
Common Lisp112Unlicense1d ago
Grade a repo

Getting noticed, but rough fundamentals could turn visitors away.

Thread-agnostic Actors in Common Lisp

Documentation

60

Contributing guide5pt0

No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).

→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.

Install and run instructions9pt45

No install instructions found in the README (−45 pts).

→ Add a section showing how to install dependencies.

README12pt75

README is present.

License6pt100

Licensed under Unlicense.

Engineering

29

CI/CD14pt0

No CI configuration detected in this repository.

→ If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.

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.

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.

Tests18pt80

Test files detected (Crypto/test).

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)
  • 11
    Forks
  • 0
    Releases

Community

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

Responsiveness

  • 12h
    Median issue response
  • —
    Median PR merge time
  • 3
    Open issues
Repository files26 root entries
  • Actors - deprecated
  • cps
  • Crypto
    Good: Test files detected (Crypto/test).
    Good: .gitignore present.
  • data-objects
  • lisp-object-encoder
  • mpcompat
  • MyKeyboards.bundle
  • ReppyChannels
  • sdle-store
  • StActors - deprecated
  • startup
  • TActors - deprecated
  • useful-macros
  • vmath
  • xTActors
  • _my_bare-startup.lisp
  • advice-trace.lisp
  • fft-fixup.lisp
  • LICENSE
    Good: Licensed under Unlicense.
  • MyKeyboards-README.txt
    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.
    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.
    Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.
    Good: README documents how to run the project.
  • project-mappings.lisp
  • project-packages-acl.cl
  • project-packages-lw.lisp
  • project-packages-sbcl.lisp
  • README.md
  • trace-find-package.lisp