paulmillr/scure-btc-signer

0

/ 100

Documentation74
Engineering72
Health100
TypeScript239MIT1d ago
Grade a repo

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

Audited & minimal library for creating, signing & decoding Bitcoin transactions.

Documentation

74

Contributing guide5pt25

Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).

→ Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.

README12pt70

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

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.

CI/CD14pt57

CI is configured (.github/workflows/test-slow.yml).

Reproducibility6pt70

Lockfile present (package-lock.json). Installs are reproducible.

Tests18pt100

Test files detected (test).

Linting and formatting5pt100

Linter or formatter configured (.prettierrc.json).

Project health

100

Dependency manifest6pt100

Dependency manifest found (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)
  • 59
    Forks
  • 29
    Releaseslatest 3y ago

Community

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

Responsiveness

  • 5h
    Median issue response
  • 2h
    Median PR merge time
  • 13
    Open issues
Repository files16 root entries
  • .github
    Good: CI is configured (.github/workflows/test-slow.yml).
  • .vscode
  • audit
  • benchmark
  • src
  • test
    Good: Test files detected (test).
  • .gitignore
    Good: .gitignore present.
  • .prettierrc.json
    Good: Linter or formatter configured (.prettierrc.json).
  • jsr.json
  • LICENSE
    Good: Licensed under MIT.
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • package.json
    Good: Dependency manifest found (package.json).
  • README-fullnode.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
    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.md
  • SECURITY.md
    Good: Security policy present.
  • tsconfig.json