tombi-toml/tombi
Grade a repo

0

/ 100

GradeB

Good community traction and solid fundamentals. Nearly in the top tier.

TOML Formatter / Linter / Language Server

Documentation56
Engineering98
Health79
Rust1,002MITtoday

Documentation

56

Install and run instructions9pt0

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

→ Add a section showing how to install dependencies.

README12pt70

README is present.

Contributing guide5pt72

CONTRIBUTING guide found.

License6pt100

Licensed under MIT.

Engineering

98

Reproducibility6pt80

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

Tests18pt100

Test files detected (crates/tombi-date-time/tests).

CI/CD14pt100

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

Linting and formatting5pt100

Linter or formatter configured (biome.json).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

79

Dependency manifest6pt55

Dependency manifest found (Cargo.toml).

Housekeeping3pt60

.gitignore present.

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • -
    Commits (30d / 90d)
  • 48
    Forks
  • 273
    Releaseslatest 1y ago

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 1,002
    Watchers

Responsiveness

  • 23h
    Median issue response
  • <1h
    Median PR merge time
  • 5
    Open issues
Repository files54 root entries
  • .cargo
  • .claude
  • .codex
  • .config
  • .github
    Good: CI is configured (.github/workflows/ci_install_script.yml).
    Good: Issue or PR templates present.
  • .vscode
  • .zed
  • blog
  • crates
    Good: Test files detected (crates/tombi-date-time/tests).
  • design
  • docs
    Good: CONTRIBUTING guide found.
    Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.
  • editors
    Issue: Build artifacts or local files may be committed (editors/intellij/.idea/gradle.xml) (−40 pts).Fix: Remove them and add to .gitignore.
  • extensions
  • python
  • rust
  • schemas
  • toml-test
  • typescript
  • www.schemastore.org
  • www.schemastore.tombi
  • xtask
  • .envrc
  • .gitcommitrule
  • .gitignore
    Good: .gitignore present.
  • .mcp.json
  • .node-version
    Good: Environment pinned via .node-version.
  • .npmrc
  • .python-version
  • AGENTS.md
  • biome.json
    Good: Linter or formatter configured (biome.json).
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • CLAUDE.md
  • clippy.toml
  • DEVELOPMENT.md
  • flake.lock
  • flake.nix
  • LICENSE
    Good: Licensed under MIT.
  • package.json
  • pnpm-lock.yaml
  • pnpm-workspace.yaml
  • pyproject.toml
  • README.md
    Good: README is present.
    Issue: README has little structure (−15 pts). Add 2-3 headings for +8 pts; 4+ earns +15 pts.Fix: Break it into sections (Overview, Install, Usage, Contributing) using Markdown headings.
    Good: README includes screenshots or visuals. Great for first impressions.
    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.
    Good: README includes status badges.
    Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • rust-toolchain.toml
  • rustfmt.toml
  • sample.md
  • sample.toml
  • snapcraft.yaml
  • tombi.code-workspace
  • tombi.toml
  • toml.ungram
  • type-test.toml
  • uv.lock
  • V2_RELEASE_TODO.md