Architecture
How the code is divided into modules and layers, and whether its dependencies point in a direction that keeps change local.
Performance
Whether the code avoids needless work, allocation and waiting on the paths that run most often.
Consistency
Whether the same problem is solved the same way across the codebase: naming, error handling, structure and conventions.
Security
How the code treats untrusted input, secrets, access control and its dependencies.
Documentation
Whether a newcomer can understand, build and use the project from its documentation and code comments.
Correctness
Whether the code does what it claims, including edge cases and error paths, and whether tests back that claim.

The score out of 100 is derived from these grades by a published rule. Read the method.