frontiercs/frontier-cs

0

/ 100

Documentation96
Engineering68
Health100
C++245MIT1d ago
Grade a repo

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

A benchmark for evaluating LLMs on open-ended CS problems. Exploring the Next Frontier of Computer Science.

Documentation

96

Install and run instructions9pt90

README documents how to install the project.

Contributing guide5pt92

Contributing guide is detailed and thorough.

README12pt100

README is present.

License6pt100

Licensed under MIT.

Engineering

68

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.

CI/CD14pt57

CI is configured (.github/workflows/check-overlap.yml).

Tests18pt80

Test files detected (adapters/frontier-cs-2.0/src/frontier_cs_2_0/task-template/tests).

Reproducibility6pt80

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

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (pyproject.toml).

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)
  • 38
    Forks
  • 1
    Releaseslatest 4mo ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 245
    Watchers

Responsiveness

  • 3h
    Median issue response
  • <1h
    Median PR merge time
  • 6
    Open issues
Repository files20 root entries
  • .github
    Good: CI is configured (.github/workflows/check-overlap.yml).
    Good: Issue or PR templates present.
  • 2.0
    Good: Licensed under MIT.
    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.
    Good: Environment pinned via 2.0/problems/duckdb_e2e_query_optimization/docker/agent/Dockerfile.
  • adapters
    Good: Test files detected (adapters/frontier-cs-2.0/src/frontier_cs_2_0/task-template/tests).
  • algorithmic
    Good: Lockfile present (algorithmic/package-lock.json). Installs are reproducible.
  • assets
  • docs
  • leaderboard
  • research
  • scripts
  • src
  • tools
  • .gitignore
    Good: .gitignore present.
  • .pre-commit-config.yaml
  • ARCHITECTURE.md
  • CONTRIBUTING.md
  • LICENSE
  • Makefile
  • pyproject.toml
    Good: Dependency manifest found (pyproject.toml).
  • 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.
  • SUBMIT.md