griddynamics/rosetta
Grade a repo

0

/ 100

GradeC

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

Top 38% of 5,156 graded repos

Meta-prompting, context engineering, and centralized instructions management for AI coding agents

Documentation92
Engineering55
Health100
TypeScript307Apache-2.01mo ago

Top fixes

Highest-impact changes first, ranked by point weight

14 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 step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.

  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

92

Contributing guide5pt67

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under Apache-2.0.

Engineering

55

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

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

Tests18pt80

Test files detected (.github/scripts/test_load_stories.py).

Reproducibility6pt80

Lockfile present (requirements.txt). Installs are reproducible.

Project health

100

Dependency manifest6pt100

Dependency manifest found (requirements.txt).

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)
  • 60
    Forks
  • 174
    Releaseslatest 4mo ago

Community

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

Responsiveness

  • <1h
    Median issue response
  • <1h
    Median PR merge time
  • 11
    Open issues
Repository files41 root entries
  • .agents
  • .claude
  • .claude-plugin
  • .cursor-plugin
  • .githooks
  • .github
    Good: Test files detected (.github/scripts/test_load_stories.py).
    Good: CI is configured (.github/workflows/validate-test-cases.yml).
  • agents
  • docs
  • instructions
  • plans
  • plugins
  • scripts
  • src
    Good: Environment pinned via src/ims-mcp-server/Dockerfile.
  • test-library
  • .cursorignore
  • .gitignore
    Good: .gitignore present.
  • CHANGELOG.md
  • CONFIGURATION.md
  • 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.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • DEPLOYMENT_GUIDE.md
  • DEVELOPER_GUIDE.md
  • ELEVATOR_SPEECH.md
  • FAQ.md
  • gain.json
  • INSTALLATION.md
  • LICENSE
    Good: Licensed under Apache-2.0.
  • llms-full.txt
  • MCPs.md
  • mypy.ini
  • NOTICE
  • OVERVIEW.md
  • PLUGINS.md
  • QUICKSTART.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.
    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.
  • requirements.txt
    Good: Lockfile present (requirements.txt). Installs are reproducible.
    Good: Dependency manifest found (requirements.txt).
  • REVIEW.md
  • run-tests.sh
  • SECURITY.md
    Good: Security policy present.
  • TROUBLESHOOTING.md
  • USAGE_GUIDE.md
  • validate-types.sh
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/griddynamics/rosetta)](https://www.repo-grade.com/report/griddynamics/rosetta)

More graded TypeScript repos