Polished and well engineered. Punching above its star count.

self-host directly in the web browser, no servers required. local-first

Documentation

88

Contributing guide5pt68

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 instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

82

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/CD14pt85

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

Reproducibility6pt85

Lockfile present (bun.lock). Installs are reproducible.

Tests18pt100

Test files detected (app/AboutDialog.e2e.test.tsx).

Linting and formatting5pt100

Linter or formatter configured (.golangci.yml).

Project health

95

Dependency manifest6pt85

Dependency manifest found (go.mod).

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)
  • 9
    Forks
  • 86
    Releaseslatest 2y ago

Community

  • Community health
  • authors own >50% of commits
  • 576
    Watchers

Responsiveness

  • 6d 3h
    Median issue response
  • <1h
    Median PR merge time
  • 1
    Open issues
Repository files57 root entries
  • .claude
  • .githooks
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
  • .vscode
  • app
    Good: Test files detected (app/AboutDialog.e2e.test.tsx).
  • auth
  • bldr
  • cmd
  • core
  • db
  • desktop
    Good: Environment pinned via desktop/Dockerfile.
  • dev
  • doc
  • e2e
  • forge
  • identity
  • lint
  • net
  • plugin
  • prototypes
  • scripts
  • sdk
  • templates
  • testbed
  • web
  • .custom-gcl.yml
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .golangci.yml
    Good: Linter or formatter configured (.golangci.yml).
  • .ignore
  • .oxfmtrc.json
  • .oxlintrc.json
  • .oxlintrc.type-aware.json
  • .protoc-manifest.json
  • AGENTS.md
  • bldr.star
  • bun.lock
    Good: Lockfile present (bun.lock). Installs are reproducible.
  • CHANGELOG.org
  • components.json
  • 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.
    Good: Contributing guide describes code style expectations.
    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.
    Good: Contributing guide includes code examples.
  • csstype-augment.d.ts
  • deps.go
  • DESIGN.md
  • global.d.ts
  • go.mod
    Good: Dependency manifest found (go.mod).
  • go.sum
  • LICENSE
    Good: Licensed under Apache-2.0.
  • meta_test.go
  • meta.go
  • package.json
  • react-doctor.config.json
  • 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.
  • tsconfig.json
  • tsconfig.net.json
  • vite.config.ts
  • vitest.browser.config.ts
  • vitest.config.ts