soneso/stellar_flutter_sdk
Grade a repo

0

/ 100

GradeB

Solid foundation. Invest in docs and CI to grow from here.

Stellar SDK for flutter - dart, Stellar, Horizon, Soneso

Documentation92
Engineering68
Health100
Dart85MITtoday

Documentation

92

Contributing guide5pt66

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

68

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.

CI/CD14pt57

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

Tests18pt80

Test files detected (android/src/test).

Reproducibility6pt82

Lockfile present (tools/xdr-generator/Gemfile.lock). Installs are reproducible.

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (android/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)
  • 36
    Forks
  • 109
    Releaseslatest 5y ago

Community

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

Responsiveness

  • 2d 17h
    Median issue response
  • 6h
    Median PR merge time
  • 0
    Open issues
Repository files29 root entries
  • .claude-plugin
  • .github
    Good: CI is configured (.github/workflows/tests.yml).
    Good: Dependabot configured for github-actions.
    Good: Issue or PR templates present.
  • android
    Good: Test files detected (android/src/test).
    Good: Dependency manifest found (android/build.gradle.kts).
  • compatibility
  • documentation
  • example
  • ios
  • lib
  • mentions
  • skills
    Good: Security policy present.
  • test
  • tools
    Good: Lockfile present (tools/xdr-generator/Gemfile.lock). Installs are reproducible.
  • xdr
  • _config.yml
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .metadata
  • .pubignore
  • analysis_options.yaml
  • CHANGELOG.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • 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.
    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.
  • LICENSE
    Good: Licensed under MIT.
  • Makefile
  • 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.
  • soroban.md
  • v3_migration_guide.md