pasta-devs/marinara-engine
Grade a repo

0

/ 100

GradeB

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

Top 30% of 5,156 graded repos

AI frontend

Documentation74
Engineering80
Health92
TypeScript440AGPL-3.01mo ago

Top fixes

Highest-impact changes first, ranked by point weight

15 to address
  1. 1
    CI/CD14pt

    Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.

  2. 2
    CI/CD14pt

    Add `pull_request:` to the workflow `on:` triggers.

  3. 3
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  4. 4
    CI/CD14pt

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

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

74

Install and run instructions9pt55

README documents how to install the project.

README12pt75

README is present.

Contributing guide5pt77

Contributing guide is detailed and thorough.

License6pt100

Licensed under AGPL-3.0.

Engineering

80

CI/CD14pt40

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

Reproducibility6pt80

Lockfile present (pnpm-lock.yaml). Installs are reproducible.

Tests18pt100

Test script and framework are configured in package.json.

Linting and formatting5pt100

Linter or formatter configured (.prettierrc).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

92

Dependency manifest6pt75

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)
  • 113
    Forks
  • 27
    Releaseslatest 3mo ago

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 440
    Watchers

Responsiveness

  • 2h
    Median issue response
  • <1h
    Median PR merge time
  • 0
    Open issues
Repository files46 root entries
  • .agents
  • .cursor
    Good: .gitignore present.
  • .github
    Good: CI is configured (.github/workflows/build-apk.yml).
    Good: Issue or PR templates present.
  • android
  • custom_components
  • docs
  • e2e
  • packages
  • pr-evidence
  • scripts
  • win
  • .dockerignore
  • .env.example
  • .gitattributes
  • .gitignore
  • .markdownlint.json
  • .npmrc
  • .nvmrc
  • .prettierignore
  • .prettierrc
    Good: Linter or formatter configured (.prettierrc).
  • AGENTS.md
  • CHANGELOG.md
  • CLAUDE.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    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.
    Good: Contributing guide includes code examples.
  • DESIGN.json
  • DESIGN.md
  • docker-compose.yml
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • Dockerfile.lite
  • hacs.json
  • LICENSE
    Good: Licensed under AGPL-3.0.
  • MarinaraLauncher.exe
  • migrate-presets.cjs
  • migrate-variables.cjs
  • package.json
    Good: Dependency manifest found (package.json).
  • playwright.config.ts
  • pnpm-lock.yaml
    Good: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
  • pnpm-workspace.yaml
  • PRODUCT.md
  • 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.
    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.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • skills-lock.json
  • start-termux.sh
  • start.bat
  • start.sh
  • tsconfig.base.json
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/pasta-devs/marinara-engine)](https://www.repo-grade.com/report/pasta-devs/marinara-engine)

More graded TypeScript repos