Standards
CodeProof separates language, standard, and rule. Only standards with an active analysis engine are enabled — everything else is clearly marked as planned.
Python
The official Python style guide covering formatting, naming, structure, and documentation conventions (via pycodestyle, pyflakes, pep8-naming, and pydocstyle rule sets).
32 rules across formatting, naming, structure, documentation
PEP 8 plus stricter documentation and structure requirements. Planned.
User-defined rule sets for classrooms and teams. Planned.
JavaScript
CodeProof's curated baseline for JavaScript — formatting, structure, and naming — running on ESLint's engine directly. Not a full eslint:recommended or style-guide reproduction.
15 rules across formatting, naming, structure, documentation
Planned.
TypeScript
The same curated formatting/structure/naming baseline as JavaScript, parsed with @typescript-eslint's parser — type-aware rules (the kind that need a full compiler setup) are not implemented yet.
19 rules across formatting, naming, structure, documentation
Java
Coming soonPlanned.
Planned.
C
Coming soonNo standards defined yet.
C++
Coming soonPlanned.
Planned.
C#
Coming soonNo standards defined yet.
Go
Coming soonNo standards defined yet.
Rust
Coming soonNo standards defined yet.
PHP
Coming soonNo standards defined yet.
Ruby
Coming soonNo standards defined yet.
Kotlin
Coming soonNo standards defined yet.
Swift
Coming soonNo standards defined yet.