masc-ucsc/livehd

0

/ 100

Documentation93
Engineering58
Health68
C++238Other1d ago
Grade a repo

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

Live Hardware Development (LiveHD), a productive infrastructure for Synthesis and Simulation

Documentation

93

Contributing guide5pt72

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under Other.

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/ubuntu.yml).

Tests18pt80

Test files detected (core/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)
  • 58
    Forks
  • 0
    Releases

Community

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

Responsiveness

  • 7d 9h
    Median issue response
  • <1h
    Median PR merge time
  • 3
    Open issues
Repository files45 root entries
  • .bernstein
  • .claude
  • .contracts
  • .github
    Good: CI is configured (.github/workflows/ubuntu.yml).
    Good: Issue or PR templates present.
  • benchmark
  • core
    Good: Test files detected (core/tests).
  • docs
    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.
    Good: Code of conduct present.
  • formal
  • graph
  • inou
  • lhd
  • lnast
  • lsp
  • packages
  • pass
  • scripts
  • soomrv
  • third_party
  • todo
  • tools
  • upass
  • ware
  • .bazelignore
  • .bazelrc
  • .bazelversion
  • .ccls
  • .clang-format
  • .clang-tidy
  • .codacy.yml
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .svlint.toml
  • .ycm_extra_conf.py
  • AGENTS.md
  • BUILD
  • check_v2prpv2.py
  • CITATION.cff
  • CLAUDE.md
  • codecov.yml
  • LICENSE
    Good: Licensed under Other.
  • MODULE.bazel
  • 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.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • renovate.json
  • STRUCTURE.md
  • WORKSPACE