Getting noticed, but rough fundamentals could turn visitors away.

All common docker scripts in one place

Documentation

66

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.

README12pt50

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

30

Tests18pt0

No tests detected anywhere in the repository.

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

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.

Reproducibility6pt30

No dependency lockfile found (−70 pts).

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

CI/CD14pt57

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

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

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

Community

  • Community health
  • authors own >50% of commits
  • 229
    Watchers

Responsiveness

  • 4d 8h
    Median issue response
  • 1d 9h
    Median PR merge time
  • 0
    Open issues
Repository files72 root entries
  • .commons
    Good: .gitignore present.
  • .envs
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
    Good: Dependabot covers 2 ecosystems (docker-compose, github-actions). Dependencies stay current.
  • .volume-backups
  • adminer
  • cassandra
  • cassandra-dse
  • elasticsearch
  • flagr
  • fluentd
  • jaeger
  • kibana
  • ldap
  • minio
  • mysql
  • mysql-slave
  • nfs-server
  • rabbitmq
  • redis
  • redis-insight
  • redis-sentinel
  • redis-slave
  • redis-stack
  • sonarqube
  • traefik
  • volumes-bnr
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .env.example
  • .gitignore
  • .yamllint.yml
  • compose.example.yaml
  • compose.networks.yaml
  • copy-examples.bat
  • copy-examples.sh
  • docker-compose.override.adminer.yml
  • docker-compose.override.apache-druid.yml
  • docker-compose.override.apache-zookeeper.yml
  • docker-compose.override.blackfire.yml
  • docker-compose.override.cassandra-dse.yml
  • docker-compose.override.cassandra.yml
  • docker-compose.override.dragonfly.yml
  • docker-compose.override.elasticsearch.yml
  • docker-compose.override.example.yml
  • docker-compose.override.flagr.yml
  • docker-compose.override.fluentd.yml
  • docker-compose.override.grafana.yml
  • docker-compose.override.jaeger.yml
  • docker-compose.override.jenkins.yml
  • docker-compose.override.ldap.yml
  • docker-compose.override.maildev.yml
  • docker-compose.override.mailhog.yml
  • docker-compose.override.minio.yml
  • docker-compose.override.mongo.yml
  • docker-compose.override.mysql.yml
  • docker-compose.override.nfs-server.yml
  • docker-compose.override.oracle.yml
  • docker-compose.override.portainer.yml
  • docker-compose.override.postgres.yml
  • docker-compose.override.rabbitmq.yml
  • docker-compose.override.redis-sentinel.yml
  • docker-compose.override.redis-stack.yml
  • docker-compose.override.redis.yml
  • docker-compose.override.redisearch.yml
  • docker-compose.override.sftp.yml
  • docker-compose.override.sonarqube.yml
  • docker-compose.override.traefik.yml
  • docker-compose.override.volumes.yml
  • docker-compose.yml
    Good: Environment pinned via docker-compose.yml.
  • LICENSE
    Good: Licensed under MIT.
  • readme.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
    Good: README has code examples.
    Issue: No live demo link in the README (−20 pts).Fix: Link to a deployed version, docs site, or demo video. Users want to see it running.
    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.
    Good: README documents how to run the project.
  • run.sh
  • validate.sh