libsgh/chrome_updater
Grade a repo

0

/ 100

GradeF

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

Higher than 42% of 5,156 graded repos

Chrome Offline Updater and Making Chrome Portable.

Documentation56
Engineering42
Health100
Go288AGPL-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 (83).

See your top fixes
Now
F
57
Potential
B
83

Top fixes

Highest-impact changes first, ranked by point weight

17 to address
  1. 1
    Tests18pt

    Add *_test.go files alongside your packages and run `go test ./...`.

  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 `pull_request:` to the workflow `on:` triggers.

  4. 4
    CI/CD14pt

    Add a lint step to catch style issues automatically.

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

56

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.

Install and run instructions9pt45

README documents how to install the project.

README12pt65

README is present.

License6pt100

Licensed under AGPL-3.0.

Engineering

42

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.

Tests18pt30

Go module found but no *_test.go files detected.

→ Add *_test.go files alongside your packages and run `go test ./...`.

CI/CD14pt40

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

Reproducibility6pt75

Lockfile present (go.sum). Installs are reproducible.

Linting and formatting5pt100

Formatting enforced (gofmt (built into Go toolchain)).

Project health

100

Dependency manifest6pt100

Dependency manifest found (go.mod).

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

Community

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

Responsiveness

  • 1d 20h
    Median issue response
  • 7h
    Median PR merge time
  • 1
    Open issues
Repository files27 root entries
  • .github
    Good: CI is configured (.github/workflows/build.yml).
  • assets
  • doc
  • lang
  • .gitignore
    Good: .gitignore present.
  • base.go
  • bean.go
  • bundle.go
  • chrome_auto_update.go
  • chrome_info.go
  • chrome_plus.go
  • common.go
  • custom_theme.go
  • data.go
  • download.go
  • FyneApp.toml
  • go.mod
    Good: Dependency manifest found (go.mod).
  • go.sum
    Good: Lockfile present (go.sum). Installs are reproducible.
  • layout.go
  • LICENSE
    Good: Licensed under AGPL-3.0.
  • locale_windows.go
  • locale.go
  • log.go
  • main.go
  • README_ZH.md
    Good: README is present.
    Issue: README is fairly short (−10 pts). At 400+ chars you get partial credit; 1,500+ earns the full +20 pts.Fix: Expand with a description, install steps, usage, and examples.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    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.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • README.md
  • setting.go
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/libsgh/chrome_updater)](https://www.repo-grade.com/report/libsgh/chrome_updater)

More graded Go repos