asciimoo/hister
Grade a repo

0

/ 100

GradeB

A well-known project done right. Strong docs and solid engineering throughout.

Top 18% of 5,156 graded repos

Your own search engine

Documentation79
Engineering88
Health100
Go1,287AGPL-3.01mo ago

Top fixes

Highest-impact changes first, ranked by point weight

6 to address
  1. 1
    README12pt

    Add CI/build status badges from shields.io or your CI provider to signal project health.

  2. 2
    Install and run instructions9pt

    Add a section showing how to install dependencies.

  3. 3
    Install and run instructions9pt

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

  4. 4
    Issue and PR templates6pt

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

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

79

Install and run instructions9pt45

No install instructions found in the README (−45 pts).

→ Add a section showing how to install dependencies.

Contributing guide5pt88

Contributing guide is detailed and thorough.

README12pt90

README is present.

License6pt100

Licensed under AGPL-3.0.

Engineering

88

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.

Tests18pt100

Test files detected (config/config_test.go).

CI/CD14pt100

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

Linting and formatting5pt100

Formatting enforced (.editorconfig).

Reproducibility6pt100

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

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)
  • 71
    Forks
  • 16
    Releaseslatest 4mo ago

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 1,287
    Watchers

Responsiveness

  • 1h
    Median issue response
  • 2h
    Median PR merge time
  • 29
    Open issues
Repository files37 root entries
  • .forgejo
  • .github
    Good: CI is configured (.github/workflows/build.yml).
    Good: Dependabot covers 4 ecosystems (gomod, npm, github-actions, nix). Dependencies stay current.
  • client
  • config
    Good: Test files detected (config/config_test.go).
  • files
  • nix
  • scripts
  • server
  • tui
  • webui
  • .dockerignore
  • .editorconfig
    Good: Formatting enforced (.editorconfig).
  • .fallowrc.json
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .golangci.toml
  • .goreleaser-rolling.yml
  • .goreleaser.yml
  • .prettierignore
  • CHANGELOG.md
  • compose.yml
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    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.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • flake.lock
  • flake.nix
  • generate.go
  • go.mod
    Good: Dependency manifest found (go.mod).
  • go.sum
    Good: Lockfile present (go.sum). Installs are reproducible.
  • hister_test.go
  • hister.go
  • LICENSE
    Good: Licensed under AGPL-3.0.
  • manage.sh
  • package-lock.json
  • package.json
  • prettier.config.js
  • 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.
    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.
    Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.
    Good: README documents how to run the project.
  • SECURITY.md
    Good: Security policy present.
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/asciimoo/hister)](https://www.repo-grade.com/report/asciimoo/hister)

More graded Go repos