imbue-ai/sculptor

0

/ 100

Documentation75
Engineering91
Health93
Python179MIT1d ago
Grade a repo

Polished and well engineered. Punching above its star count.

Build product with grounded, parallel coding agents.

Documentation

75

README12pt55

README is present.

Contributing guide5pt67

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

91

Reproducibility6pt80

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

CI/CD14pt85

CI is configured (.github/workflows/build-desktop.yml).

Tests18pt95

Test files detected (scripts/compute_pi_pin_test.py).

Linting and formatting5pt100

Linter or formatter configured (sculptor/frontend/.prettierrc.cjs).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

93

Dependency manifest6pt78

Dependency manifest found (pyproject.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)
  • 9
    Forks
  • 7
    Releaseslatest 1d ago

Community

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

Responsiveness

  • 2d 1h
    Median issue response
  • 1h
    Median PR merge time
  • 15
    Open issues
Repository files41 root entries
  • .claude
  • .devcontainer
    Good: Environment pinned via .devcontainer/Dockerfile.
  • .githooks
  • .github
    Good: CI is configured (.github/workflows/build-desktop.yml).
    Good: Issue or PR templates present.
  • .sculptor
  • .vscode
  • agent_docs
  • container
  • docs
  • ratchets
  • samples
  • scripts
    Good: Test files detected (scripts/compute_pi_pin_test.py).
  • sculptor
    Good: Linter or formatter configured (sculptor/frontend/.prettierrc.cjs).
  • tools
  • .cursorignore
  • .dockerignore
  • .envrc
  • .gitattributes
  • .gitconfig
  • .gitignore
    Good: .gitignore present.
  • .python-version
  • .ratchetignore
  • CLAUDE.md
  • codex-output-schema.json
  • CONTRIBUTING.md
    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.
  • depot.json
  • justfile
  • LICENSE.md
    Good: Licensed under MIT.
  • offload-electron.toml
  • offload-history.jsonl
  • offload-unit.toml
  • offload.toml
  • openhost.Dockerfile
  • openhost.toml
  • pyproject.toml
    Good: Dependency manifest found (pyproject.toml).
  • pyrefly.toml
  • ratchet-counts.toml
  • ratchets.toml
  • README.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.
    Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    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.
  • SECURITY.md
    Good: Security policy present.
  • uv.lock
    Good: Lockfile present (uv.lock). Installs are reproducible.