Getting some notice. Tests and CI would be the fastest wins.

Community website for Collabora Online: Build Collabora Online; Build for Android; Build for iOS; FAQ; Communication channels; etc

Documentation

70

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.

README12pt70

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

A license file is present.

Engineering

21

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.

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/CD14pt40

CI is configured (.github/workflows/sync-build-readme.yml).

Reproducibility6pt80

Lockfile present (themes/hugo-theme-chunky-poster/yarn.lock). Installs are reproducible.

Project health

100

Dependency manifest6pt100

Dependency manifest found (themes/hugo-theme-chunky-poster/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)
  • 35
    Forks
  • 0
    Releases

Community

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

Responsiveness

  • 3d 5h
    Median issue response
  • 16h
    Median PR merge time
  • 6
    Open issues
Repository files15 root entries
  • .claude
  • .github
    Good: CI is configured (.github/workflows/sync-build-readme.yml).
  • archetypes
  • content
    Good: A license file is present.
  • data
  • layouts
  • scripts
  • static
  • themes
    Good: Lockfile present (themes/hugo-theme-chunky-poster/yarn.lock). Installs are reproducible.
    Good: Environment pinned via themes/hugo-theme-chunky-poster/.nvmrc.
    Good: Dependency manifest found (themes/hugo-theme-chunky-poster/package.json).
  • .gitignore
    Good: .gitignore present.
  • .hugo_build.lock
  • config.toml
  • configTaxo.toml
  • deploy.sh
  • 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.