sari3l/poc-monitor
Grade a repo

54

/ 100

GradeF

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

Higher than 39% of 5,156 graded repos

๐Ÿ” Github CVE POC ไฟกๆฏ็›‘ๆŽงๆŽจ้€ ๐Ÿš€

Documentation44
Engineering42
Health100
Go410GPL-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 C (79).

See your top fixes
Now
F
54
Potential
C
79

Top fixes

Highest-impact changes first, ranked by point weight

18 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

44

Install and run instructions9pt0

No install instructions found in the README (โˆ’45 pts).

โ†’ Add a section showing how to install dependencies.

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.

README12pt68

README is present.

License6pt100

Licensed under GPL-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/schedule.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

  • 432 / 2252
    Commits (30d / 90d)
  • 68
    Forks
  • 0
    Releases

Community

  • 42% - Weak
    Community health
  • 1 bus factorlow
    author own >50% of commits
  • 410
    Watchers

Responsiveness

  • 4h
    Median issue response
  • -
    Median PR merge time
  • 0
    Open issues
Repository files43 root entries
  • .github
    Good: CI is configured (.github/workflows/schedule.yml).
  • 18
  • 2000
  • 2001
  • 2002
  • 2003
  • 2004
  • 2005
  • 2006
  • 2007
  • 2008
  • 2009
  • 2010
  • 2011
  • 2012
  • 2013
  • 2014
  • 2015
  • 2016
  • 2017
  • 2018
  • 2019
  • 202
  • 2020
  • 2021
  • 2022
  • 2023
  • 2024
  • 2025
  • 2026
  • 9
  • dateLog
  • .gitignore
    Good: .gitignore present.
  • blacklist.yaml
  • go.mod
    Good: Dependency manifest found (go.mod).
  • go.sum
    Good: Lockfile present (go.sum). Installs are reproducible.
  • LICENSE
    Good: Licensed under GPL-3.0.
  • new.json
  • README.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.
    Issue: README has some structure (โˆ’7 pts). 2-3 headings earns partial credit; 4+ earns the full +15 pts.Fix: Add more sections (Overview, Install, Usage, Contributing) using ## headings.
    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.
    Good: README includes status badges.
    Issue: No install instructions found in the README (โˆ’45 pts).Fix: Add a section showing how to install dependencies.
    Issue: No run or usage instructions found (โˆ’45 pts).Fix: Add a section showing how to start or use the project.
  • search.go
  • update.go
  • update.json
  • utils.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/sari3l/poc-monitor)](https://www.repo-grade.com/report/sari3l/poc-monitor)

More graded Go repos