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

A pure Dart WebAssembly runtime for Dart and Flutter ecosystems.

Documentation

65

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.

Install and run instructions9pt45

README documents how to install the project.

README12pt80

README is present.

License6pt100

Licensed under MIT.

Engineering

29

CI/CD14pt0

No CI configuration detected in this repository.

If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.

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.

Reproducibility6pt0

No dependency lockfile found (−70 pts).

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

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.

Tests18pt80

Test files detected (example/doom/ios/RunnerTests/RunnerTests.swift).

Project health

100

Dependency manifest6pt100

Dependency manifest found (example/doom/android/app/build.gradle.kts).

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)
  • 1
    Forks
  • 2
    Releaseslatest 3mo ago

Community

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

Responsiveness

  • <1h
    Median issue response
  • <1h
    Median PR merge time
  • 0
    Open issues
Repository files17 root entries
  • docs
  • example
    Good: Test files detected (example/doom/ios/RunnerTests/RunnerTests.swift).
    Good: Dependency manifest found (example/doom/android/app/build.gradle.kts).
  • lib
  • test
  • third_party
  • tool
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • AGENTS.md
  • analysis_options.yaml
  • CHANGELOG.md
  • CLAUDE.md
  • dart_test.yaml
  • LICENSE
    Good: Licensed under MIT.
  • pubspec.lock
  • pubspec.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.
    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.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.