tempoxyz/tempo-apps

0

/ 100

Documentation59
Engineering100
Health89
TypeScript194Apache-2.01d ago
Grade a repo

Polished and well engineered. Punching above its star count.

Monorepo for Tempo Apps

Documentation

59

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.

README12pt55

README is present.

Install and run instructions9pt55

No install instructions found in the README (−45 pts).

→ Add a section showing how to install dependencies.

License6pt100

Licensed under Apache-2.0.

Engineering

100

Tests18pt100

Test files detected (apps/contract-verification/scripts/precompile-seed/seed.test.ts).

CI/CD14pt100

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

Linting and formatting5pt100

Linter or formatter configured (biome.json).

Reproducibility6pt100

Lockfile present (pnpm-lock.yaml). Installs are reproducible.

Issue and PR templates6pt100

Issue or PR templates present.

Project health

89

Dependency manifest6pt65

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)
  • 111
    Forks
  • 0
    Releases

Community

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

Responsiveness

  • 6d 24h
    Median issue response
  • 1h
    Median PR merge time
  • 25
    Open issues
Repository files18 root entries
  • .github
    Good: CI is configured (.github/workflows/main.yml).
    Good: Dependabot covers 3 ecosystems (npm, github-actions, docker). Dependencies stay current.
    Good: Issue or PR templates present.
  • .vscode
  • .zed
  • apps
    Good: Test files detected (apps/contract-verification/scripts/precompile-seed/seed.test.ts).
    Good: Environment pinned via apps/contract-verification/Dockerfile.
  • packages
  • patches
  • scripts
  • .git-blame-ignore-revs
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • AGENTS.md
  • biome.json
    Good: Linter or formatter configured (biome.json).
  • LICENSE-APACHE
  • LICENSE-MIT
  • package.json
    Good: Dependency manifest found (package.json).
  • pnpm-lock.yaml
    Good: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
  • pnpm-workspace.yaml
  • 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.
    Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.
    Good: README documents how to run the project.