nextcloud/activity
Grade a repo

83

/ 100

GradeB

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

Top 26% of 5,156 graded repos

:zap: Activity app for Nextcloud

Documentation67
Engineering87
Health100
JavaScript1401mo ago

Top fixes

Highest-impact changes first, ranked by point weight

13 to address
  1. 1
    Tests18pt

    Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.

  2. 2
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  3. 3
    README12pt

    Show a quick-start snippet so contributors can see what using your project looks like.

  4. 4
    Install and run instructions9pt

    Add a .env.example listing all required environment variables so contributors know what to set up.

Working through the fixes? Let every push regrade itself.

The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

67

License6pt0

No license detected.

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

Contributing guide5pt61

Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.

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

README12pt85

README is present.

Install and run instructions9pt90

README documents how to install the project.

Engineering

87

Tests18pt80

Test files detected (playwright/e2e/admin-settings.spec.ts).

CI/CD14pt85

CI is configured (.github/workflows/lint-info-xml.yml).

Reproducibility6pt90

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

Linting and formatting5pt100

PHP linting configured (eslint.config.js).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (composer.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

  • 44 / 152
    Commits (30d / 90d)
  • 70
    Forks
  • 0
    Releases

Community

  • 62% - Fair
    Community health
  • -
    authors own >50% of commits
  • 140
    Watchers

Responsiveness

  • 6h
    Median issue response
  • 1h
    Median PR merge time
  • 149
    Open issues
Repository files36 root entries
  • .github
    Good: CI is configured (.github/workflows/lint-info-xml.yml).
    Good: Dependabot covers 2 ecosystems (composer, composer). Dependencies stay current.
    Good: Issue or PR templates present.
  • .tx
  • appinfo
  • css
  • docs
  • img
  • js
  • l10n
  • lib
  • LICENSES
  • playwright
    Good: Test files detected (playwright/e2e/admin-settings.spec.ts).
  • src
  • templates
  • tests
  • vendor-bin
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .l10nignore
  • .php-cs-fixer.dist.php
  • AUTHORS.md
  • composer.json
    Good: Dependency manifest found (composer.json).
  • composer.lock
    Good: Lockfile present (composer.lock). Installs are reproducible.
  • CONTRIBUTING.md
    Issue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +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.
  • eslint.config.js
    Good: PHP linting configured (eslint.config.js).
  • Makefile
  • package-lock.json
  • package.json
  • playwright.config.ts
  • pr-body.md
  • psalm.xml
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    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.
  • renovate.json
  • REUSE.toml
  • stylelint.config.cjs
  • tsconfig.json
  • vite.config.ts
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/nextcloud/activity)](https://www.repo-grade.com/report/nextcloud/activity)

More graded JavaScript repos