rtvkiz/minimal

0

/ 100

Documentation95
Engineering16
Health68
Shell492Other1d ago
Grade a repo

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

Minimal CVE Hardened container image collection

Documentation

95

Contributing guide5pt88

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under Other.

Engineering

16

Tests18pt0

No tests detected anywhere in the repository.

→ Add automated tests. They prove the code works and give contributors confidence to make changes.

Linting and formatting5pt0

No linter or formatter config found.

→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.

Reproducibility6pt0

No dependency lockfile found (−70 pts).

→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.

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.

CI/CD14pt57

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

Project health

68

Dependency manifest6pt0

No dependency manifest detected at root.

→ Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.

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)
  • 21
    Forks
  • 0
    Releases

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 492
    Watchers

Responsiveness

  • 7h
    Median issue response
  • 16h
    Median PR merge time
  • 2
    Open issues
Repository files65 root entries
  • .github
    Good: CI is configured (.github/workflows/build.yml).
    Good: Security policy present.
  • alertmanager
  • assets
  • bun
  • caddy
  • consul
  • coredns
  • cuda-python
  • deno
  • docs
  • dotnet
  • envoy
  • etcd
  • fluent-bit
  • gitea
  • go
  • haproxy
  • helm
  • httpd
  • jaeger
  • java
  • jenkins
  • kafka
  • keycloak
  • kubectl
  • loki
  • mailpit
  • mariadb
  • memcached
  • mimir
  • minio
  • mosquitto
  • mysql
  • nats
  • nginx
  • node-slim
  • openbao
  • opensearch
  • opentofu
  • otelcol
  • php
  • postgres-slim
  • prometheus
  • python
  • qdrant
  • rabbitmq
  • rails
  • redis-slim
  • registry
  • ruby
  • sqlite
  • telegraf
  • tempo
  • thanos
  • tools
  • traefik
  • trivy
  • valkey
  • vex
  • victoria-metrics
  • .gitignore
    Good: .gitignore present.
  • 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.
  • LICENSE
    Good: Licensed under Other.
  • Makefile
  • 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.