solsynth/solian
Grade a repo

0

/ 100

GradeD

Popular for its size, but the engineering basics lag behind the interest.

Top 47% of 5,156 graded repos

All in one frontend for the Solar Network

Documentation89
Engineering51
Health79
Dart276AGPL-3.01mo ago

A low grade is a to-do list, not a judgment of your code

Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to B (89).

See your top fixes
Now
D
69
Potential
B
89

Top fixes

Highest-impact changes first, ranked by point weight

14 to address
  1. 1
    Tests18pt

    Set scripts.test in package.json to your actual test command, e.g. "vitest" or "jest".

  2. 2
    CI/CD14pt

    Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.

  3. 3
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  4. 4
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

Working through the fixes? Let every push regrade itself.

The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

89

Contributing guide5pt30

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.

README12pt100

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under AGPL-3.0.

Engineering

51

Linting and formatting5pt0

No linter or formatter found.

→ Add ESLint (eslint.config.js) and/or Prettier (.prettierrc), install them as devDependencies, and add a `lint` script to package.json.

Tests18pt35

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

CI/CD14pt57

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

Reproducibility6pt80

Lockfile present (package-lock.json). Installs are reproducible.

Issue and PR templates6pt100

Issue or PR templates present.

Project health

79

Dependency manifest6pt55

Dependency manifest found (package.json).

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)
  • 31
    Forks
  • 97
    Releaseslatest 1y ago

Community

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

Responsiveness

  • 4h
    Median issue response
  • 5h
    Median PR merge time
  • 1
    Open issues
Repository files33 root entries
  • .github
    Good: CI is configured (.github/workflows/build.yml).
    Good: Issue or PR templates present.
  • .vscode
  • android
  • assets
  • buildtools
    Good: Environment pinned via buildtools/flatpak/Dockerfile.
  • docs
  • drift_schemas
  • ios
    Good: Test files detected (ios/RunnerTests/RunnerTests.swift).
  • lib
  • linux
  • macos
  • node_modules
    Issue: Build artifacts or local files may be committed (node_modules/.cache) (−40 pts).Fix: Remove them and add to .gitignore.
  • packages
  • plans
  • test
  • web
  • windows
  • .gitignore
    Good: .gitignore present.
  • .locmanrc
  • .metadata
  • analysis_options.yaml
  • build.yaml
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • devtools_options.yaml
  • firebase.json
  • LICENSE.txt
    Good: Licensed under AGPL-3.0.
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • package.json
    Good: Dependency manifest found (package.json).
  • pubspec.lock
  • pubspec.yaml
  • README_CN.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.
  • README.md
  • setup.iss
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/solsynth/solian)](https://www.repo-grade.com/report/solsynth/solian)

More graded Dart repos