apache/skywalking-website

0

/ 100

Documentation82
Engineering60
Health97
CSS106Apache-2.01d ago
Grade a repo

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

Apache SkyWalking Website

Documentation

82

README12pt70

README is present.

Contributing guide5pt77

CONTRIBUTING guide found.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

60

Tests18pt35

Test files detected (themes/docsy/assets/vendor/bootstrap/js/tests).

CI/CD14pt57

CI is configured (.github/workflows/deploy.yaml).

Reproducibility6pt70

Lockfile present (themes/docsy/assets/vendor/bootstrap/Gemfile.lock). Installs are reproducible.

Linting and formatting5pt100

Linter or formatter configured (themes/docsy/assets/vendor/bootstrap/.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

97

Dependency manifest6pt92

Dependency manifest found (package.json).

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

Community

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

Responsiveness

  • —
    Median issue response
  • <1h
    Median PR merge time
  • 1
    Open issues
Repository files20 root entries
  • .github
    Good: CI is configured (.github/workflows/deploy.yaml).
  • assets
  • content
  • data
  • layouts
  • scripts
  • static
  • themes
    Good: CONTRIBUTING guide found.
    Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.
    Good: Code of conduct present.
    Good: Test files detected (themes/docsy/assets/vendor/bootstrap/js/tests).
    Good: Linter or formatter configured (themes/docsy/assets/vendor/bootstrap/.editorconfig).
    Good: Lockfile present (themes/docsy/assets/vendor/bootstrap/Gemfile.lock). Installs are reproducible.
    Good: Issue or PR templates present.
  • .asf.yaml
  • .gitignore
    Good: .gitignore present.
  • .htaccess
  • .hugo_build.lock
  • CLAUDE.md
  • config.toml
  • doc.sh
  • docs.js
  • LICENSE
    Good: Licensed under Apache-2.0.
  • netlify.toml
  • package.json
    Good: Dependency manifest found (package.json).
  • 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.