quarkusio/quarkusio.github.io

0

/ 100

Documentation60
Engineering78
Health100
HTML1851d ago
Grade a repo

Good shape overall. A few tweaks would push it into the top tier.

Website for Quarkus project

Documentation

60

License6pt0

No license detected.

→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.

Contributing guide5pt55

CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.

→ Add setup instructions, code style notes, and how to run tests.

README12pt70

README is present.

Install and run instructions9pt90

README documents how to install the project.

Engineering

78

Linting and formatting5pt0

No Java/Kotlin linter configured.

→ Add Checkstyle or Spotless for Java formatting, or ktlint/Detekt for Kotlin. Run it via Maven/Gradle or as a CI step.

Tests18pt80

Test files detected (_guides/_examples/acme-serve-http-requests-MyAcmeApplicationTest.java).

CI/CD14pt85

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

Reproducibility6pt100

Lockfile present (Gemfile.lock). Installs are reproducible.

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (Gemfile).

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

Community

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

Responsiveness

  • 3h
    Median issue response
  • <1h
    Median PR merge time
  • 181
    Open issues
Repository files95 root entries
  • _data
  • _generated-doc
  • _guides
    Good: Test files detected (_guides/_examples/acme-serve-http-requests-MyAcmeApplicationTest.java).
  • _includes
  • _layouts
  • _plugins
  • _posts
  • _redirects
    Good: Security policy present.
  • _sass
  • _versions
  • .github
    Good: CI is configured (.github/workflows/build.yml).
    Good: Dependabot covers 2 ecosystems (maven, github-actions). Dependencies stay current.
    Good: Issue or PR templates present.
  • .well-known
  • assets
  • contributors
  • jekyll-container
  • newsletter
  • specs
  • src
  • tools
  • working-groups
  • _config_dev.yml
  • _config.yml
  • _noguides_config.yml
  • _only_latest_guides_config.yml
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitleaks.toml
  • 1kcontributors.md
  • 404.md
  • about.md
  • ai-agentic.md
  • ai-ai-blueprints.md
  • ai-blueprints-chainofthought.md
  • ai-blueprints-contextualrag.md
  • ai-blueprints-frozenrag.md
  • ai-chain-of-thought.md
  • ai-contextual-rag.md
  • ai-getting-started-with-ai.md
  • ai-java-for-ai.md
  • ai-overview.md
  • ai-quarkus-for-ai.md
  • author.md
  • benefactors.md
  • blog.md
  • books.md
  • brand.md
  • CNAME
  • components.md
  • container-first.md
  • continuum.adoc
  • CONTRIBUTING.md
    Issue: CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +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.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    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).
    Good: Contributing guide describes the PR/review workflow.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • desktopwallpapers.md
  • developer-joy.md
  • discussion.md
  • docker-compose_with_guides.yml
  • docker-compose.yml
    Good: Environment pinned via docker-compose.yml.
  • events.md
  • faq.adoc
  • favicon.ico
  • feed.xml
  • fetchpub.java
  • foundation-faq.md
  • foundation.md
  • Gemfile
    Good: Dependency manifest found (Gemfile).
  • Gemfile.lock
    Good: Lockfile present (Gemfile.lock). Installs are reproducible.
  • get-started.md
  • index.md
  • insights.md
  • kubernetes-native.md
  • newsletter.md
  • performance.md
  • pom.xml
  • qtips.md
  • quarkus2.md
  • quarkus3.md
  • 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.
    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.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • robots.txt
  • security-openid-connect-web-authentication.md
  • security.adoc
  • serve-noguides.sh
  • serve-only-latest-guides.sh
  • serve.sh
  • sitemap.md
  • sitemap.xml
  • socials.md
  • spring-migrate.md
  • spring.md
  • standards.md
  • stickers.md
  • support.md
  • unlinkedguides.java
  • usage_policy.md
  • usage.md
  • userstories.md
  • wg.md