© 2026 GitRating by Mozen.in. All rights reserved.
Aravind S — Engineering Score: 18/100 (Beginner) | GitRating
Public Profile
Aravind S 3 Repos
0 Followers
2 Following
18
out of 100
Beginner
Confidence 35% · Low
Language Capabilities
Most used overall JavaScript 55% 3 languages coded
Overall Summary
Portfolio consists of three small, zero-star, unlicensed repositories with no tests, no CI/CD, no documentation (except one README), and no version control discipline visible. The projects appear to be beginner tutorial-level exercises (calculator, rock-paper-scissors) with one slightly more substantial JavaScript project (Vectus-2.0) that still lacks tests, licensing, and deployment readiness.
Vectus-2.0 includes a README, showing awareness that documentation matters All three repos have issues enabled, indicating some intent for project tracking • No tests detected in any of the three repositories (calculator, rock-paper-scissors, Vectus-2.0) • No license file in any repository, making all code technically all-rights-reserved and unusable by others Category Breakdown — evidence for every score
Architecture 15 Confidence 30% · Low
Evidence
calculator is a single HTML file project with no visible separation of concerns rock-paper-scissors is similarly a single HTML file with no modular structure Vectus-2.0 uses JavaScript but no architectural patterns (caching, queueing, pagination) are detectable from repo metadata Repository Intelligence
Estimated Repository Score
Know your own score. Connect GitHub and get your explainable Engineering Score in 60 seconds. Free.
Get your GitRating
• No README in calculator or rock-paper-scissors, providing zero setup or usage context
• No CI/CD pipeline, Dockerfile, or deployment configuration detected in any repo
• No topics or descriptions set on any repository, reducing discoverability and signaling lack of project packaging discipline
• Zero stars and zero forks across all repos, indicating no community engagement or peer review +3 Add MIT license to all three repositories
No license detected in calculator, rock-paper-scissors, or Vectus-2.0; without a license the code is legally unusable by others
+4 Write README files for calculator and rock-paper-scissors
calculator and rock-paper-scissors have no README; Vectus-2.0 demonstrates the developer can produce one
+5 Add unit tests to Vectus-2.0
Vectus-2.0 is the most substantial project (JavaScript, has README) but has zero test coverage; adding tests would demonstrate engineering maturity
+3 Set up GitHub Actions CI for Vectus-2.0
No CI/CD detected in any repo; Vectus-2.0 is the best candidate to start with given it has a README
+1 Add repository topics and descriptions to all repos
All three repos have no topics set; adding them improves discoverability and shows project packaging awareness
•
Separation of concerns
• Dependency direction discipline
• Scalability signals
• Config/secrets handling
• Consistent patterns across codebase Recommendations
Refactor Vectus-2.0 into modular file structure +5 Vectus-2.0 is JavaScript and the best candidate to demonstrate architectural thinking
Backend 5 Confidence 40% · Low
Evidence
No backend code detected in any of the three repositories All repos are HTML or JavaScript with no server, API, or database files visible Missing
• API design • Database usage • Server patterns • Authentication Recommendations
Build a small backend API project +10 No backend evidence exists across calculator, rock-paper-scissors, or Vectus-2.0; a simple Express.js API would demonstrate backend competency
Code Quality 20 Confidence 25% · Low
Evidence
Cannot assess code quality directly without file contents; repos are small enough that quality is likely basic No linting configuration files detected in repo metadata Missing
• Naming conventions evidence • Function/file size discipline • DRY principle evidence • Error handling patterns • Type safety (TypeScript) Recommendations
Add ESLint and Prettier to Vectus-2.0 +4 No linting detected in Vectus-2.0; adding ESLint/Prettier would enforce consistent code quality
Complexity & Judgment 15 Confidence 20% · Low
Evidence
calculator and rock-paper-scissors are common tutorial/beginner projects, suggesting tutorial-following rather than original problem-solving Vectus-2.0 is slightly more original but still small in scope No evidence of tradeoff analysis or architectural decision records Missing
• Right-sized solution evidence • Tradeoff awareness documentation • Original problem-solving vs tutorial-following Recommendations
Build an original project that solves a real problem +8 calculator and rock-paper-scissors are tutorial-level; an original project would demonstrate genuine engineering judgment
DevOps 0 Confidence 50% · Medium
Evidence
No CI/CD pipeline detected in any of the three repos No Dockerfile detected in any repo No IaC (Terraform, CloudFormation, etc.) detected No monitoring/logging hooks visible Missing
• CI/CD pipeline • Dockerfile • IaC • Environment separation • Monitoring/logging Recommendations
Add a GitHub Actions workflow to Vectus-2.0 +5 No CI/CD in any repo; Vectus-2.0 is the best starting point given it has a README and uses JavaScript
Documentation 15 Confidence 45% · Low
Evidence
Vectus-2.0 has a README file calculator has no README rock-paper-scissors has no README No API docs, changelog, or versioning discipline detected in any repo Missing
• README in calculator and rock-paper-scissors • Inline comments explaining WHY • API docs / type exports • Changelog / versioning Recommendations
Create README.md for calculator and rock-paper-scissors +5 calculator and rock-paper-scissors both lack READMEs; Vectus-2.0 shows the developer can produce one
Frontend 25 Confidence 35% · Low
Evidence
calculator uses HTML, indicating basic HTML/CSS/JS frontend work rock-paper-scissors uses HTML, another frontend project Vectus-2.0 uses JavaScript, suggesting more frontend logic than the HTML-only repos Missing
• UI framework usage (React, Vue, Angular, Svelte) • Component quality signals • CSS architecture • Responsive design evidence Recommendations
Migrate calculator or rock-paper-scissors to a component framework like React +6 Both calculator and rock-paper-scissors are plain HTML; using a modern framework would demonstrate component-based architecture
Maintainability 10 Confidence 30% · Low
Evidence
No commit history visible in metadata to assess commit message quality No PR discipline visible (zero forks, zero stars, no contributors) No refactoring evidence detectable from metadata No topics or descriptions on repos, suggesting limited project management discipline Missing
• Commit message quality evidence • PR discipline • Refactoring evidence • Dead code cleanup evidence Recommendations
Adopt conventional commit messages +3 No commit message quality evidence across any of the three repos; adopting a standard would improve maintainability
Security 15 Confidence 30% · Low
Evidence
No authentication code visible in any repo No dependency files (package.json with lockfile) visible in repo metadata for calculator or rock-paper-scissors Cannot assess committed secrets without file access but no .env.example or secrets management detected Missing
• Auth quality assessment • Input validation/sanitization • Dependency hygiene • Secrets management Recommendations
Add input sanitization to Vectus-2.0 +3 Vectus-2.0 is JavaScript and likely handles user input; no sanitization patterns detected
Testing 0 Confidence 45% · Low
Evidence
No test files detected in calculator No test files detected in rock-paper-scissors No test files detected in Vectus-2.0 No CI configuration that could run tests in any repo Missing
• Any test files • Edge-case coverage • Unit/integration/e2e mix • CI running tests Recommendations
Add Jest tests to Vectus-2.0 +8 Vectus-2.0 has zero tests; it is the most substantial project and the best candidate for introducing testing
10
Strengths
Issues are enabled, showing some intent for project tracking
Weaknesses
No README file · No license file · No test files · No CI/CD or deployment configuration · No topics set on repository
Estimated Repository Score
Strengths
Issues are enabled
Weaknesses
No README file · No license file · No test files · No CI/CD or deployment configuration · No topics set on repository
Estimated Repository Score
Strengths
Has a README file, unlike the other two repos · Uses JavaScript, suggesting more logic than the HTML-only repos · Issues are enabled
Weaknesses
No test files detected · No license file · No CI/CD or deployment configuration · No topics set on repository · No linting or formatting configuration detected
