mwt-proger/imageproxy
Grade a repo

0

/ 100

GradeB

Solid engineering. The main gap is visibility.

Top 28% of 5,156 graded repos

A caching, resizing image proxy written in Go

Documentation91
Engineering87
Health55
0Apache-2.03y ago

Top fixes

Highest-impact changes first, ranked by point weight

13 to address
  1. 1
    Install and run instructions9pt

    Add a .env.example listing all required environment variables so contributors know what to set up.

  2. 2
    Reproducibility6pt

    Add additional package-ecosystem entries (especially github-actions) to keep all dependencies current.

  3. 3
    Issue and PR templates6pt

    Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.

  4. 4
    Issue and PR templates6pt

    A SECURITY.md explains how to responsibly disclose vulnerabilities. Worth adding once the project has real users.

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

91

Contributing guide5pt61

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 Apache-2.0.

Engineering

87

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.

Reproducibility6pt97

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

Tests18pt100

Test files detected (cache_test.go).

CI/CD14pt100

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

Linting and formatting5pt100

Formatting enforced (.golangci.yml).

Project health

55

Activity5pt5

No pushes in over 2 years. Looks unmaintained (−95 pts).

→ A recent commit signals the project is alive and worth using.

Housekeeping3pt40

No .gitignore found (−60 pts).

→ Add a .gitignore to keep build output, node_modules, and secrets out of version control.

Repository metadata5pt60

Repository has a description.

Dependency manifest6pt100

Dependency manifest found (go.mod).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • -
    Commits (30d / 90d)
  • 0
    Forks
  • 0
    Releases

Community

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

Responsiveness

  • -
    Median issue response
  • -
    Median PR merge time
  • 0
    Open issues
Repository files22 root entries
  • .github
    Good: CI is configured (.github/workflows/linter.yml).
    Good: Dependabot configured for gomod.
  • caddy
  • cmd
  • docs
    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.
    Good: Contributing guide describes code style expectations.
    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).
    Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • etc
  • internal
  • third_party
  • .golangci.yml
    Good: Formatting enforced (.golangci.yml).
  • cache_test.go
    Good: Test files detected (cache_test.go).
  • cache.go
  • data_test.go
  • data.go
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • go.mod
    Good: Dependency manifest found (go.mod).
  • go.sum
    Good: Lockfile present (go.sum). Installs are reproducible.
  • imageproxy_test.go
  • imageproxy.go
  • LICENSE
    Good: Licensed under Apache-2.0.
  • metrics.go
  • 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.
  • transform_test.go
  • transform.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/mwt-proger/imageproxy)](https://www.repo-grade.com/report/mwt-proger/imageproxy)

More graded repos