Ram karthick P — Engineering Score: 18/100 (Beginner) | GitRating
Public Profile
Ram karthick P
6Repos
1Followers
1Following
18
out of 100
Beginner
Confidence35% · Low
Skill Radar
Language Capabilities
Most used overallJavaScript95%4 languages coded
JavaScript
95%
HTML
4%
CSS
0%
TypeScript
0%
Overall Summary
Portfolio of small, tutorial-level front-end projects with no testing, no CI/CD, no licensing, and minimal documentation. No evidence of backend work, system design, security practices, or deployment readiness. The developer appears to be in an early learning phase.
Strengths
Multiple repos created showing initiative to build and publish projects (Happyver-media-site, AgriMarket, portfolio, d-portfolio)
Profile repo (Ramkarthick1525/Ramkarthick1525) correctly uses github-config topics for profile customization
Some repos include README files (Happyver-media-site, AgriMarket, portfolio, d-portfolio) indicating basic awareness of documentation
Missing
Category Breakdown — evidence for every score
Architecture 15Confidence30% · Low
Evidence
All repos are small front-end projects with no detectable separation of concerns or layered architecture
No evidence of caching, queueing, pagination, or rate-limiting in any repo
No config/secrets management patterns visible in any repository
•Zero tests detected across all 6 repositories — no unit, integration, or e2e tests in any repo
•No CI/CD pipeline, Dockerfile, or IaC detected in any repository
•No licenses on any repository including those with functional code (Happyver-media-site, AgriMarket)
•html_form and Ramkarthick1525/Ramkarthick1525 lack README files entirely
•No evidence of backend development, API design, database usage, or authentication in any repo
•No topics or descriptions on project repos limiting discoverability and context
•Zero stars, zero forks, and only 1 follower across all repos indicating no community engagement or peer review
Recommendations
+3
Add LICENSE files to all code repositories
Happyver-media-site, AgriMarket, portfolio, and d-portfolio all lack licenses, making them legally unusable by others
+8
Add a testing framework and write at least one test per repo
No tests exist in any of the 6 repos; adding Jest or similar to Happyver-media-site and AgriMarket would demonstrate quality discipline
+5
Set up GitHub Actions CI for JavaScript repos
Happyver-media-site, AgriMarket, and d-portfolio have no CI pipeline; a basic lint+test workflow would show DevOps awareness
+2
Add README to html_form repo
html_form has no README, leaving visitors with no context on purpose, setup, or usage
+1
Add topics and descriptions to project repos
Happyver-media-site and AgriMarket have no topics or descriptions, reducing discoverability and professional presentation
•
Separation of concerns
•Dependency direction abstractions
•Scalability signals
•Config/secrets handling
Recommendations
Introduce a clear folder structure in AgriMarket+5
AgriMarket appears to be the most complex project; separating concerns into src/components, src/utils, src/services would demonstrate architectural thinking
Backend 0Confidence40% · Low
Evidence
No backend code, API endpoints, database connections, or server patterns detected in any of the 6 repositories
All repos are either front-end JavaScript/HTML or a profile config repo
Missing
•API design
•Database usage
•Server patterns
•Authentication
Recommendations
Build a small backend API for AgriMarket+10
AgriMarket (an agricultural market app) would benefit from a backend API for product listings; adding Express.js with a simple CRUD endpoint would demonstrate backend capability
Code Quality 20Confidence25% · Low
Evidence
No linter configuration (.eslintrc, .prettierrc) detected in any repo
No TypeScript detected in any repository
Cannot verify naming conventions, function sizes, or DRY adherence without deeper code access
Missing
•Linting configuration
•TypeScript type safety
•Error handling patterns
•DRY utility extraction
Recommendations
Add ESLint and Prettier to Happyver-media-site and AgriMarket+5
No linting or formatting config detected; adding these would enforce consistent code quality across JavaScript repos
Complexity & Judgment 15Confidence20% · Low
Evidence
Projects appear to be tutorial-level or beginner exercises (portfolio, html_form, d-portfolio)
No evidence of tradeoff analysis or architectural decision records
Cannot reliably assess problem-solving depth from repo metadata alone
No evidence of right-sizing solutions or original problem-solving vs tutorial-following
Missing
•Architectural decision records
•Tradeoff documentation
•Evidence of original problem-solving
•Right-sized solution judgment
Recommendations
Build an original project that solves a real problem+8
Current repos (portfolio, html_form, d-portfolio) appear tutorial-level; building AgriMarket into a real agricultural marketplace with genuine problem-solving would demonstrate engineering judgment
DevOps 0Confidence45% · Low
Evidence
No .github/workflows directory or CI/CD config detected in any repo
No Dockerfile, docker-compose, or IaC (Terraform, CloudFormation) in any repo
No environment separation (dev/staging/prod) signals
No monitoring/logging hooks detected
Missing
•CI/CD pipeline
•Dockerfile or IaC
•Environment separation
•Monitoring/logging
Recommendations
Add a GitHub Actions workflow to Happyver-media-site+5
Happyver-media-site has no CI; a basic workflow that runs lint and build on push would show DevOps readiness
Documentation 20Confidence40% · Low
Evidence
4 of 6 repos have README files (Happyver-media-site, AgriMarket, portfolio, d-portfolio)
html_form and Ramkarthick1525/Ramkarthick1525 lack READMEs entirely
No API docs, changelogs, or versioning discipline detected in any repo
Cannot verify README quality or whether setup instructions actually work
Missing
•README on html_form
•README on Ramkarthick1525/Ramkarthick1525
•Inline comments explaining WHY
•API documentation
•Changelog/versioning
Recommendations
Write detailed READMEs for AgriMarket and Happyver-media-site+5
These repos have READMEs but quality is unknown; ensuring they include working setup instructions, screenshots, and project descriptions would improve documentation scores
Frontend 30Confidence35% · Low
Evidence
Happyver-media-site and AgriMarket use JavaScript indicating some front-end interactivity
portfolio and d-portfolio are HTML-based personal portfolio sites
html_form demonstrates basic HTML form construction
Missing
•Modern UI frameworks (React, Vue, Angular)
•Component architecture
•CSS architecture (BEM, Tailwind, CSS modules)
•Responsive design signals
Recommendations
Migrate d-portfolio to a component-based framework like React+8
d-portfolio uses vanilla JavaScript; migrating to React with reusable components would demonstrate modern front-end skills
Maintainability 15Confidence30% · Low
Evidence
No commit message quality signals available from metadata
No PR discipline visible (0 forks, 1 follower, no collaborators)
No refactoring evidence over time detectable from repo metadata
No .gitignore or editorconfig detected to enforce consistent development environment
Missing
•Meaningful commit messages
•PR discipline
•Refactoring evidence
•Dead code cleanup
Recommendations
Adopt conventional commits and add .gitignore to JavaScript repos+3
Happyver-media-site, AgriMarket, and d-portfolio lack .gitignore; adding one and following conventional commit format would improve maintainability
Security 10Confidence30% · Low
Evidence
No authentication code detected in any repo
No input validation or sanitization patterns visible
No dependency lock files or audit configurations detected
Cannot confirm or rule out committed secrets without deeper file access
Missing
•Authentication implementation
•Input validation/sanitization
•Dependency hygiene (outdated packages, CVEs)
•Secrets management
Recommendations
Add input validation to html_form+3
html_form is an HTML form project with no visible validation; adding client-side and server-side validation would demonstrate security awareness
Testing 0Confidence45% · Low
Evidence
No test files, test directories, or test configuration detected in any of the 6 repositories
No package.json test scripts or testing dependencies visible in repo metadata
No CI configuration that could run tests
Missing
•Unit tests
•Integration tests
•E2E tests
•Edge-case coverage
•CI test execution
Recommendations
Add Jest tests to AgriMarket for core utility functions+10
AgriMarket has zero tests; adding even a single test suite for market calculation logic would move testing from 0 to a demonstrable practice
20
Maintainability
15
Strengths
Has a README file indicating some documentation awareness · Uses JavaScript suggesting front-end interactivity beyond static HTML
Weaknesses
No tests, no CI/CD, no license · No topics or description for discoverability · No linting or type safety configuration detected
Has a README file · Project concept (agricultural market) suggests attempt at a real-world application rather than a simple exercise
Weaknesses
No tests, no CI/CD, no license · No backend or API detected for what should be a data-driven application · No topics or description limiting context and discoverability
Has a README file · Demonstrates HTML/CSS skills for personal branding
Weaknesses
No tests, no CI/CD, no license · Portfolio sites are common tutorial projects with limited complexity signal · No modern framework or component architecture detected
