haiwen/seahub
Grade a repo

0

/ 100

GradeC

Good shape overall. A few tweaks would push it into the top tier.

Top 41% of 5,156 graded repos

The web end of seafile server.

Documentation59
Engineering77
Health94
JavaScript596Other1mo ago

Top fixes

Highest-impact changes first, ranked by point weight

13 to address
  1. 1
    Tests18pt

    Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.

  2. 2
    README12pt

    Break it into sections (Overview, Install, Usage, Contributing) using Markdown headings.

  3. 3
    README12pt

    Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.

  4. 4
    README12pt

    Show a quick-start snippet so contributors can see what using your project looks like.

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

59

Contributing guide5pt0

No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).

→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.

README12pt40

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Other.

Engineering

77

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.

Reproducibility6pt70

Lockfile present (requirements.txt). Installs are reproducible.

Tests18pt80

Test files detected (frontend/src/tests).

CI/CD14pt100

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

Linting and formatting5pt100

Linter or formatter configured (frontend/.eslintrc.json).

Project health

94

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt100

Dependency manifest found (requirements.txt).

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)
  • 393
    Forks
  • 353
    Releaseslatest 11y ago

Community

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

Responsiveness

  • 5h
    Median issue response
  • 7h
    Median PR merge time
  • 129
    Open issues
Repository files35 root entries
  • .github
    Good: CI is configured (.github/workflows/test.yml).
  • .tx
  • bin
  • fabfile
  • frontend
    Good: Test files detected (frontend/src/tests).
    Good: Linter or formatter configured (frontend/.eslintrc.json).
    Issue: Build artifacts or local files may be committed (frontend/.env) (−40 pts).Fix: Remove them and add to .gitignore.
  • locale
  • media
  • scripts
  • seahub
  • sql
  • static
  • tests
  • thirdpart
  • tools
  • .gitignore
    Good: .gitignore present.
  • .travis.yml.bak
  • code-check.sh
  • CONTRIBUTORS
  • dev-requirements.txt
  • HACKING
  • i18n.sh
  • LICENSE-thirdparty.txt
  • LICENSE.txt
    Good: Licensed under Other.
  • Makefile
  • manage.py
  • pylintrc
  • pylintrc.template
  • pytest.ini
  • README.markdown
    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.
    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.
    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.
    Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • requirements.txt
    Good: Lockfile present (requirements.txt). Installs are reproducible.
    Good: Dependency manifest found (requirements.txt).
  • run-seahub.sh.template
  • sdoc-helper.sh
  • send_user_notifications.sh.template
  • setenv.sh.template
  • test-requirements.txt
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/haiwen/seahub)](https://www.repo-grade.com/report/haiwen/seahub)

More graded JavaScript repos