Sign in

Use the email address and password you were given.

c2cedge Repo Scorer

2-hour hackathon · code evidence + hiring rubric

Students0
Repos scored0
Judged0
Avg code score–
Repo errors0

Cohorts & people

Cohorts

A cohort is one college's batch for one event. Every submission belongs to one, and judges only see their own.

People

Everyone signs in with their own email and password, so a saved score always names a real person. Learners are created automatically when you upload them.

Upload learners

One learner per line: Name, Email, Phone, GitHub URL. Commas or tabs both work, so you can paste rows straight from a sheet. A header row is skipped, and a repo or email already in the cohort is not added twice. Each learner with an email gets a sign-in so they can read their own report.

#StudentRepoCode scoreRubric scoreOverallStatus

No students yet

Choose Add students and paste the list of names, USNs and GitHub links. Each repo is checked automatically as soon as it is added.

How the scores work
  • Code score (out of 100) is automatic. Each repo is cloned and checked for the playbook's must-haves: README, login, OTP/MFA, role checks, validation, database, AI integration and guardrails, error handling, tests, deploy config, secrets hygiene, commit history and structure.
  • Rubric score (out of 100) comes from judges: technical execution 25%, problem understanding 15%, feasibility 15%, communication 15%, solution quality 10%, innovation 10%, user impact 10%. Each criterion is scored 0–10.
  • Overall is the average of the two once both exist; until then it shows whichever score is available.