fossasia/eventyay
Grade a repo

0

/ 100

GradeB

A well-known project done right. Strong docs and solid engineering throughout.

Top 20% of 5,156 graded repos

Open Source Event Management, Ticketing and Checkins, Talks and Schedules, Video and Interpretations, Badges, Exhibitions and more https://eventyay.com

Documentation73
Engineering88
Health100
Python1,629Apache-2.01mo ago

Top fixes

Highest-impact changes first, ranked by point weight

11 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
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

  4. 4
    README12pt

    Break it into sections (Overview, Install, Usage, Contributing) using Markdown headings.

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

73

README12pt40

README is present.

Contributing guide5pt87

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

88

Tests18pt80

Test files detected (.agents/skills/django-add-form/tests).

CI/CD14pt85

CI is configured (.github/workflows/test-collection.yml).

Linting and formatting5pt100

Linter or formatter configured (app/eventyay/webapp/schedule-editor/.editorconfig).

Reproducibility6pt100

Lockfile present (app/eventyay/webapp/schedule-editor/package-lock.json). Installs are reproducible.

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (app/eventyay/webapp/schedule-editor/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)
  • 393
    Forks
  • 0
    Releases

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 1,629
    Watchers

Responsiveness

  • 17d 15h
    Median issue response
  • 12d 21h
    Median PR merge time
  • 106
    Open issues
Repository files21 root entries
  • .agents
    Good: Test files detected (.agents/skills/django-add-form/tests).
  • .github
    Good: CI is configured (.github/workflows/test-collection.yml).
    Good: Dependabot covers 5 ecosystems (uv, npm, npm, npm, npm). Dependencies stay current.
    Good: Issue or PR templates present.
  • app
    Good: Linter or formatter configured (app/eventyay/webapp/schedule-editor/.editorconfig).
    Good: Lockfile present (app/eventyay/webapp/schedule-editor/package-lock.json). Installs are reproducible.
    Good: Environment pinned via app/Dockerfile.
    Good: Dependency manifest found (app/eventyay/webapp/schedule-editor/package.json).
  • deployment
  • doc
  • tools
  • .cursorrules
  • .dockerignore
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • agents.md
  • CLA.md
  • CLAUDE.md
  • CODEX.md
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Good: Contributing guide explains how to run tests.
    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.
  • deb-packages.txt
  • DEPLOYMENT.md
  • docker-compose.yml
  • LICENSE
    Good: Licensed under Apache-2.0.
  • NOTICE
  • README.rst
    Good: README is present.
    Issue: README has little structure (−15 pts). Add 2-3 headings for +8 pts; 4+ earns +15 pts.Fix: Break it into sections (Overview, Install, Usage, Contributing) using Markdown headings.
    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.
    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.
    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.
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/fossasia/eventyay)](https://www.repo-grade.com/report/fossasia/eventyay)

More graded Python repos