objeck/objeck-lang
Grade a repo

0

/ 100

GradeB

Polished and well engineered. Punching above its star count.

Top 18% of 5,156 graded repos

Lightweight object-oriented and functional programming language. Designed to be intuitive, small, cross-platform, and fast. The language emphasizes portability, scalability, and robust API support.

Documentation93
Engineering78
Health100
C++165Other1mo 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 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

93

Contributing guide5pt74

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.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under Other.

Engineering

78

CI/CD14pt57

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

Tests18pt80

Test files detected (core/lib/matrix/lib/eigen-3.4.0/test).

Reproducibility6pt80

Lockfile present (programs/web-playground/backend/requirements.txt). Installs are reproducible.

Linting and formatting5pt100

Linter or formatter configured (tools/lsp/clients/vscode/.eslintrc.js).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (core/compiler/compiler.sln).

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)
  • 13
    Forks
  • 177
    Releaseslatest 10y ago

Community

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

Responsiveness

  • 5h
    Median issue response
  • 2h
    Median PR merge time
  • 0
    Open issues
Repository files23 root entries
  • .claude
  • .github
    Good: CI is configured (.github/workflows/ci-build.yml).
    Good: Issue or PR templates present.
  • .vscode
  • core
    Good: Test files detected (core/lib/matrix/lib/eigen-3.4.0/test).
    Good: Dependency manifest found (core/compiler/compiler.sln).
  • docker
    Good: Environment pinned via docker/Dockerfile.
  • docs
  • perf-results
  • programs
    Good: Lockfile present (programs/web-playground/backend/requirements.txt). Installs are reproducible.
  • scripts
  • tools
    Good: Linter or formatter configured (tools/lsp/clients/vscode/.eslintrc.js).
  • .dockerignore
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitleaks.toml
  • CHANGELOG.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • 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.
    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.
  • LICENSE
    Good: Licensed under Other.
  • PERF_DEBUG_CONTEXT.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.
  • run_codedoc.bat
  • SECURITY.md
    Good: Security policy present.
  • SIGNING.md
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/objeck/objeck-lang)](https://www.repo-grade.com/report/objeck/objeck-lang)

More graded C++ repos