HARIHARAN P — Engineering Score: 22/100 (Beginner) | GitRating
Public Profile
HARIHARAN P
8Repos
0Followers
2Following
22
out of 100
Beginner
Confidence35% · Low
Skill Radar
Language Capabilities
Most used overallTypeScript43%8 languages coded
TypeScript
43%
Java
29%
CSS
11%
JavaScript
8%
HTML
6%
Batchfile
2%
Dockerfile
Overall Summary
Portfolio of small, tutorial-scale projects with no tests, no CI/CD, no licensing, and minimal community engagement (0 stars, 0 forks, 0 followers). Demonstrates basic full-stack awareness (Java, JavaScript, TypeScript, HTML/CSS) but lacks engineering rigor across every measured axis.
Strengths
Exposure to multiple languages (Java in AI-Powered-Expense-Analyzer, TypeScript in newprojectmadads, JavaScript in UserDB_Manager) suggests willingness to learn diverse ecosystems
My_Personal_Portfolio has a clear description stating responsive design with Home, About, Skills, Projects, Contact sections, showing basic product thinking
Food-Delivery-Landing-Page- description explicitly scopes the project as a simple dynamic website, showing honest self-assessment of project complexity
Missing
Category Breakdown — evidence for every score
Architecture 18Confidence30% · Low
Evidence
AI-Powered-Expense-Analyzer uses Java suggesting possible layered architecture but no evidence of design patterns
UserDB_Manager in JavaScript implies a database interaction pattern but no evidence of separation of concerns
newprojectmadads uses TypeScript which enables better structural typing but no evidence of architectural patterns
•Zero tests detected across all 8 repositories — no test files, no test scripts, no CI pipeline running tests
•No LICENSE in any repository, making all code technically all-rights-reserved and unusable by others
•My_Personal_Portfolio is missing a README entirely, making it impossible for visitors to understand setup or purpose without reading source
•UserDB_Manager and User_DB_Manager appear to be duplicate or near-duplicate repos, suggesting poor project hygiene and version control discipline
•Hari10012001/Hari10012001 and Hari10012001/sample have no language detected and are likely empty or placeholder repos — dead weight in the profile
•No topics set on any repository, reducing discoverability and suggesting lack of project curation
•0 stars and 0 forks across all repos indicates no external validation or community adoption
Recommendations
+3
Add LICENSE files to all repositories
No LICENSE detected in any of the 8 repos (AI-Powered-Expense-Analyzer, My_Personal_Portfolio, UserDB_Manager, etc.), making code legally unusable by others
+2
Add README to My_Personal_Portfolio
My_Personal_Portfolio is the only repo with Has README: NO — a portfolio site should showcase documentation ability
+2
Delete or consolidate placeholder repos (Hari10012001/Hari10012001 and Hari10012001/sample)
Both repos have Language: N/A and no description, signaling no meaningful content; removing them improves profile signal-to-noise ratio
+2
Consolidate UserDB_Manager and User_DB_Manager into a single repository
Two repos with nearly identical names (UserDB_Manager and User_DB_Manager) both in JavaScript suggest duplication; consolidate to show version control discipline
+5
Add at least one test file to the most substantial project (AI-Powered-Expense-Analyzer or newprojectmadads)
Zero tests across all repos is the strongest negative signal; adding even basic unit tests to AI-Powered-Expense-Analyzer (Java) or newprojectmadads (TypeScript) would demonstrate testing awareness
+1
Set repository topics on all projects for discoverability
All 8 repos have Topics: none; adding topics like 'java', 'expense-tracker', 'portfolio' improves GitHub profile professionalism
•No evidence of dependency injection
•No evidence of layered/clean architecture
•No evidence of caching, queueing, pagination, or rate-limiting
•No evidence of config/secrets separation
•No evidence of consistent patterns across repos
Recommendations
Document architectural decisions in AI-Powered-Expense-Analyzer README+3
No architecture documentation detected; adding a simple architecture diagram and rationale would demonstrate design thinking
Backend 20Confidence30% · Low
Evidence
UserDB_Manager (JavaScript) name implies database management functionality
newprojectmadads (TypeScript) may include backend components
Missing
•No evidence of REST API design or OpenAPI/Swagger docs
•No evidence of authentication implementation
•No evidence of proper database schema design or migrations
•No evidence of server framework usage (Express, Spring, etc.)
•No evidence of input validation middleware
Recommendations
Add API documentation to UserDB_Manager+4
UserDB_Manager implies database/API operations but no API docs detected; adding endpoint documentation would demonstrate backend competence
Code Quality 18Confidence25% · Low
Evidence
TypeScript usage in newprojectmadads suggests some type safety awareness
Multiple language repos suggest adaptability but no evidence of consistent code standards
No linter or formatter configs detected in any repo
Missing
•No evidence of linting (ESLint, Checkstyle, Prettier)
•No evidence of DRY principle application (UserDB_Manager vs User_DB_Manager duplication concern)
•No evidence of meaningful error handling
•No evidence of function/file size discipline
•No evidence of consistent naming conventions
Recommendations
Add ESLint and Prettier configs to newprojectmadads and UserDB_Manager+4
No linter/formatter detected in any JavaScript/TypeScript repo; adding these would demonstrate code quality tooling awareness
Complexity & Judgment 20Confidence20% · Low
Evidence
Food-Delivery-Landing-Page- description honestly scopes the project as 'simple dynamic website' — shows self-awareness
My_Personal_Portfolio uses appropriate technology (HTML/CSS/JS) for a portfolio site — not over-engineered
AI-Powered-Expense-Analyzer name suggests an appropriately scoped project for a learning context
Missing
•No evidence of tradeoff analysis or decision documentation
•No evidence of choosing appropriate libraries over hand-rolled solutions
•No evidence of original problem-solving vs tutorial-following
•No evidence of right-sized architecture decisions
•Insufficient data to reliably assess this axis — scored conservatively
Recommendations
Add a 'Design Decisions' section to AI-Powered-Expense-Analyzer README explaining technology choices+2
No evidence of tradeoff awareness documentation; adding rationale for why Java was chosen and what alternatives were considered would demonstrate engineering judgment
DevOps 5Confidence35% · Low
Evidence
No CI/CD pipeline detected in any repository
No Dockerfile or docker-compose detected
No infrastructure-as-code files detected
No deployment configuration detected
Missing
•CI/CD pipeline (GitHub Actions, etc.)
•Docker/containerization
•Environment separation (dev/staging/prod)
•Monitoring/logging hooks
•Deployment automation
Recommendations
Add a GitHub Actions workflow to AI-Powered-Expense-Analyzer for build and test+5
No CI/CD detected anywhere; adding a basic GitHub Actions workflow to the Java project would demonstrate DevOps awareness
Documentation 15Confidence40% · Low
Evidence
6 of 8 repos have README files (My_Personal_Portfolio does not, Hari10012001/profile repo does)
My_Personal_Portfolio has a description but no README — worst case for a portfolio project
Food-Delivery-Landing-Page- has a description but README quality unknown
No repos have topics set, reducing discoverability
Missing
•No evidence of setup instructions that actually work
•No evidence of inline comments explaining design decisions
•No API documentation
•No changelog or versioning discipline
•No architecture decision records
Recommendations
Write comprehensive README for My_Personal_Portfolio with setup, screenshots, and live demo+4
My_Personal_Portfolio is the only repo with no README; a portfolio site should be the best-documented project in the profile
Frontend 25Confidence35% · Low
Evidence
My_Personal_Portfolio (CSS) description mentions responsive design with clean UI and project highlights
Food-Delivery-Landing-Page- (HTML) is a frontend landing page project
Portfolio description mentions HTML, CSS, and JavaScript with device optimization
Missing
•No evidence of modern frontend framework (React, Vue, Angular) usage
•No evidence of CSS architecture (BEM, Tailwind, CSS modules)
•No evidence of component-based design
•No evidence of accessibility considerations
•No evidence of state management patterns
Recommendations
Add a live demo link or screenshots to My_Personal_Portfolio README+3
Portfolio has no README at all; adding screenshots and a live demo link would showcase frontend work visually
Maintainability 12Confidence30% · Low
Evidence
UserDB_Manager and User_DB_Manager appear to be duplicate repos, indicating poor project management
Hari10012001/Hari10012001 and Hari10012001/sample appear to be empty/placeholder repos
No evidence of commit message quality (no access to commit history in provided data)
No evidence of PR discipline or code review
Missing
•No evidence of meaningful commit messages
•No evidence of PR-based development
•No evidence of refactoring over time
•No evidence of issue tracking usage despite Issues being enabled
•No evidence of dead code cleanup
Recommendations
Remove placeholder repos and consolidate duplicates+3
Hari10012001/Hari10012001 and Hari10012001/sample have no detectable content; UserDB_Manager and User_DB_Manager are likely duplicates — cleaning these up improves maintainability signal
Security 10Confidence30% · Low
Evidence
No authentication implementation visible in any repo
UserDB_Manager name implies user data handling but no evidence of security practices
No security-related topics or descriptions on any repo
Missing
•No evidence of password hashing
•No evidence of input sanitization
•No evidence of secrets management (env vars, .gitignore for secrets)
•No evidence of dependency vulnerability scanning
•No evidence of auth/session management
Recommendations
Add .gitignore and environment variable handling to UserDB_Manager+3
UserDB_Manager handles user data but no evidence of secrets protection or .gitignore configuration detected
Testing 0Confidence40% · Low
Evidence
No test files detected in any of the 8 repositories
No CI/CD pipeline detected that could run tests
No test scripts or test dependencies mentioned in any repo
Missing
•Unit tests
•Integration tests
•End-to-end tests
•Test coverage reporting
•CI pipeline executing tests
•Any testing framework (JUnit, Jest, Mocha, etc.)
Recommendations
Add JUnit tests to AI-Powered-Expense-Analyzer+8
Java project with zero tests; adding even basic JUnit tests for expense logic would be the single highest-impact improvement across the entire profile
25
Maintainability
15
Strengths
Java usage suggests exposure to a strongly-typed, enterprise-relevant language · Project name implies a practical, real-world use case (expense analysis with AI)
Weaknesses
No LICENSE file detected · No test files detected · No CI/CD pipeline detected · README exists but quality and content unknown · No topics set for discoverability
Description clearly articulates the project scope: responsive portfolio with Home, About, Skills, Projects, Contact, and resume · Appropriate technology choice (HTML/CSS/JS) for a portfolio site — not over-engineered
Weaknesses
No README file — critical gap for a portfolio project that should showcase documentation ability · No LICENSE file detected · No test files detected · No CI/CD pipeline detected · No topics set for discoverability
JavaScript usage suggests web development awareness · Project name implies database management functionality
Weaknesses
Appears to be duplicated by User_DB_Manager repo — poor version control hygiene · No LICENSE file detected · No test files detected · No CI/CD pipeline detected · No evidence of input validation or secrets handling for a user database manager
No language detected — likely empty or minimal content · No LICENSE file detected · No test files detected · No CI/CD pipeline detected · Appears to be a default GitHub profile repo with no engineering value
TypeScript usage suggests awareness of type safety · Has a README file
Weaknesses
No LICENSE file detected · No test files detected · No CI/CD pipeline detected · No topics set for discoverability · Project name 'newprojectmadads' is not descriptive
No language detected — likely empty or minimal content · No LICENSE file detected · No test files detected · No CI/CD pipeline detected · Repo name 'sample' suggests throwaway code
JavaScript usage suggests web development awareness · Has a README file
Weaknesses
Appears to be a duplicate of UserDB_Manager — poor project hygiene · No LICENSE file detected · No test files detected · No CI/CD pipeline detected · No evidence of security practices for user data management
Description honestly scopes the project as a 'simple dynamic website using HTML and CSS' · Appropriate technology choice for a landing page — not over-engineered · Has a README file
Weaknesses
No LICENSE file detected · No test files detected · No CI/CD pipeline detected · No JavaScript framework usage detected for a 'dynamic' website · No topics set for discoverability