t-unit/tonik
Grade a repo

0

/ 100

GradeD

Getting some notice. Tests and CI would be the fastest wins.

Pure Dart OpenAPI 3.0/3.1 code generator. Creates type-safe API client packages for Dart and Flutter with sealed classes, pattern matching, and full encoding support.

Documentation95
Engineering48
Health62
Dart11MITtoday

Documentation

95

Contributing guide5pt86

Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.

→ Add setup instructions, code style notes, and how to run tests.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under MIT.

Engineering

48

Linting and formatting5pt0

No linter or formatter config found.

→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.

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.

Reproducibility6pt20

No dependency lockfile found (−70 pts).

→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.

CI/CD14pt57

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

Tests18pt80

Test files detected (integration_test/additional_properties/additional_properties_test/test).

Project health

62

Dependency manifest6pt0

No dependency manifest detected at root.

→ Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.

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)
  • 3
    Forks
  • 17
    Releaseslatest 6mo ago

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 11
    Watchers

Responsiveness

  • 10h
    Median issue response
  • <1h
    Median PR merge time
  • 0
    Open issues
Repository files23 root entries
  • .claude
  • .github
    Good: CI is configured (.github/workflows/lint.yml).
    Good: Dependabot covers 7 ecosystems (github-actions, pub, pub, pub, pub, pub, pub). Dependencies stay current.
  • .idea
    Issue: Build artifacts or local files may be committed (.idea/.name) (−40 pts).Fix: Remove them and add to .gitignore.
  • .vscode
  • docs
  • integration_test
    Good: Test files detected (integration_test/additional_properties/additional_properties_test/test).
  • packages
  • resources
  • scripts
  • .fvmrc
  • .gitignore
    Good: .gitignore present.
  • .mcp.json
  • AGENTS.md
  • analysis_options.yaml
  • CHANGELOG.md
  • CLAUDE.md
  • codecov.yml
  • CONTRIBUTING.md
    Issue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.
    Good: Contributing guide includes setup/install instructions.
    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.
  • LICENSE
    Good: Licensed under MIT.
  • melos_tonik_workspace.iml
  • melos_tonik.iml
  • pubspec.yaml
  • 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.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.