b-m-capital-research/honeclaw
Grade a repo

84

/ 100

GradeB

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

Top 24% of 5,156 graded repos

HoneClaw (Hone-Financial) is dedicated to being a professional investment assistant that truly understands you.

Documentation90
Engineering80
Health86
Rust738MIT1mo ago

Top fixes

Highest-impact changes first, ranked by point weight

16 to address
  1. 1
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  2. 2
    CI/CD14pt

    Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.

  3. 3
    README12pt

    Add CI/build status badges from shields.io or your CI provider to signal project health.

  4. 4
    Reproducibility6pt

    Add a Dockerfile, .nvmrc, or .python-version to pin the runtime version and make the environment reproducible.

Working through the fixes? Let every push regrade itself.

The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

90

Contributing guide5pt60

CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.

→ Add setup instructions, code style notes, and how to run tests.

README12pt90

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

80

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 (Cargo.lock). Installs are reproducible.

CI/CD14pt85

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

Tests18pt100

Test files detected (packages/app/e2e/company-profile-transfer.spec.ts).

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Project health

86

Dependency manifest6pt55

Dependency manifest found (Cargo.toml).

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)
  • 109
    Forks
  • 74
    Releaseslatest 3mo ago

Community

  • 87% - Good
    Community health
  • -
    authors own >50% of commits
  • 738
    Watchers

Responsiveness

  • <1h
    Median issue response
  • <1h
    Median PR merge time
  • 25
    Open issues
Repository files46 root entries
  • .agents
  • .claude
  • .codex
  • .githooks
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
  • .vscode
  • agents
  • bins
  • crates
  • docs
  • memory
  • packages
    Good: Test files detected (packages/app/e2e/company-profile-transfer.spec.ts).
  • resources
  • scripts
  • skills
  • tests
  • workflows
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .env.example
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitleaksignore
  • AGENTS.md
  • bun.lock
  • bunfig.toml
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • CASES_EN.md
  • CASES_ZH.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • config.example.yaml
  • CONTRIBUTING.md
    Issue: CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.
    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.
    Good: Contributing guide explains how to run tests.
    Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • fix_logs.py
  • GEMINI.md
  • gitleaks.toml
  • launch.sh
  • LICENSE
    Good: Licensed under MIT.
  • logo.svg
  • make_dmg_release.sh
  • package.json
  • README_EN.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.
  • README_ZH.md
  • README.md
  • SECURITY.md
    Good: Security policy present.
  • soul.md
  • tsconfig.base.json
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/b-m-capital-research/honeclaw)](https://www.repo-grade.com/report/b-m-capital-research/honeclaw)

More graded Rust repos