ifer47/markeron
Grade a repo

80

/ 100

GradeA

Exemplary work. Strong across project hygiene, engineering, and documentation.

Top 3% of 5,156 graded repos

Lightweight (~1.5 MB) open-source screen annotation with click-through mode and keyboard-first shortcuts. For demos, teaching, meetings & screen recording. Windows, macOS.

Documentation97
Engineering98
Health100
TypeScript1,186MIT1mo ago

Outstanding. A score of 98/100 puts this repo in a very small tier of truly well-engineered projects.

Top fixes

Highest-impact changes first, ranked by point weight

3 to address
  1. 1
    Install and run instructions9pt

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

  2. 2
    Reproducibility6pt

    Add .github/dependabot.yml with at least one package-ecosystem entry, or a renovate.json, so dependencies are updated automatically.

  3. 3
    Contributing guide5pt

    Describe your linting/formatting rules and how to run them.

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

97

Install and run instructions9pt90

README documents how to install the project.

Contributing guide5pt97

Contributing guide is detailed and thorough.

README12pt100

README is present.

License6pt100

Licensed under MIT.

Engineering

98

Reproducibility6pt80

Lockfile present (package-lock.json). Installs are reproducible.

Tests18pt100

Test files detected (scripts/merge-updater-json.test.mjs).

CI/CD14pt100

CI is configured (.github/workflows/ci.yml).

Linting and formatting5pt100

Linter or formatter configured (.prettierrc).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

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)
  • 79
    Forks
  • 96
    Releaseslatest 7mo ago

Community

  • 100% - Good
    Community health
  • 1 bus factorlow
    author own >50% of commits
  • 1,186
    Watchers

Responsiveness

  • 2d 1h
    Median issue response
  • 2h
    Median PR merge time
  • 25
    Open issues
Repository files36 root entries
  • .cursor
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
    Good: Issue or PR templates present.
  • .husky
  • .vscode
  • assets
  • docs
  • packaging
  • promo
  • public
  • scripts
    Good: Test files detected (scripts/merge-updater-json.test.mjs).
  • src
  • src-tauri
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .node-version
    Good: Environment pinned via .node-version.
  • .npmrc
  • .nvmrc
  • .prettierignore
  • .prettierrc
    Good: Linter or formatter configured (.prettierrc).
  • AGENTS.md
  • appxmanifest.xml
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • commitlint.config.js
  • 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.
    Good: Contributing guide includes code examples.
  • index.html
  • LICENSE
    Good: Licensed under MIT.
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • package.json
    Good: Dependency manifest found (package.json).
  • PRIVACY.md
  • README_zh.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Good: README has code examples.
    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.
  • README.md
  • SECURITY.md
    Good: Security policy present.
  • tsconfig.json
  • tsconfig.node.json
  • vite.config.ts
  • vitest.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/ifer47/markeron)](https://www.repo-grade.com/report/ifer47/markeron)

More graded TypeScript repos