Public Profile

G-dharan

7Repos

0Followers

0Following

out of 100

Junior

Confidence35% · Low

Skill Radar

Language Capabilities

Most used overallJava100%1 languages coded

Java

100%

Overall Summary

Developer shows foundational Java skills through multiple small projects (TicTacToe, ParkingLot, BookMyShow) but lacks production-readiness signals across all repositories: no tests, no CI/CD, no licensing, and no community engagement (0 stars, 0 forks, 0 followers). The portfolio is consistent with an early-career developer building learning exercises rather than shipping maintainable software.

Strengths

Consistent use of Java across 6 of 7 repositories (PhysioApp, PaymentService, ProductCatalog, TicTacToe, ParkingLot, BookMyShow) demonstrates language focus and persistence
Every project repository has a README file, indicating awareness of project documentation basics
Repository naming conventions are clear and descriptive (PaymentService, ProductCatalog, ParkingLot, BookMyShow) suggesting domain awareness

Category Breakdown — evidence for every score

Architecture 30Confidence30% · Low

Evidence

Repository names suggest domain separation (PaymentService, ProductCatalog, ParkingLot, BookMyShow) but no code-level architecture evidence is available from inventory data
G-dharan/G-dharan profile config repo shows minimal but appropriate separation of concerns for config files

Missing

•No evidence of dependency injection patterns
•No evidence of layered architecture (controller/service/repository)

Repository Intelligence

G-dharan/PhysioApp25

Estimated Repository Score

Architecture

Documentation

Testing

Deployment

Security

Complexity

Know your own score.

Connect GitHub and get your explainable Engineering Score in 60 seconds. Free.

Get your GitRating

Download this report

Missing

•Zero test files detected across any repository — no unit, integration, or e2e tests in PhysioApp, PaymentService, ProductCatalog, TicTacToe, ParkingLot, or BookMyShow
•No CI/CD pipeline evidence in any repository (no .github/workflows, no Jenkinsfile, no Dockerfile detected in any repo)
•No licenses on any repository including all 6 Java projects, making code legally unusable by others
•Zero community engagement across all repos (0 stars, 0 forks, 0 followers) suggests no peer review or collaboration has occurred
•No topics or descriptions on project repos (PaymentService, ProductCatalog, ParkingLot, TicTacToe) limiting discoverability and context
•No evidence of dependency management best practices (no visible pom.xml or build.gradle analysis, no dependency pinning signals)

Recommendations

Add unit tests to at least one Java repository

Zero tests across all repos (PhysioApp, PaymentService, ProductCatalog, TicTacToe, ParkingLot, BookMyShow) is the single largest gap; adding JUnit tests to ParkingLot or BookMyShow would demonstrate testing competency

Set up GitHub Actions CI for build and test

No CI/CD detected in any repository; adding a simple Maven/Gradle build workflow to PaymentService or ProductCatalog would show DevOps awareness

Add open-source licenses to all public repositories

All 7 repos including G-dharan/PhysioApp and G-dharan/BookMyShow have no license, which legally restricts usage and signals incomplete project hygiene

Add topics and descriptions to project repositories

PaymentService, ProductCatalog, TicTacToe, ParkingLot, and BookMyShow have no topics or descriptions, reducing discoverability and context for reviewers

Add Dockerfiles to at least 2 backend service repos

PaymentService and ProductCatalog appear to be backend services but have no containerization evidence, limiting deployment readiness

Backend 32Confidence30% · Low

Evidence

Java used across 6 repos suggesting backend language proficiency
PaymentService and ProductCatalog names suggest API/service development experience
BookMyShow and ParkingLot suggest experience with transactional backend domains

Missing

•No evidence of REST API design patterns
•No evidence of database usage (no SQL files, no ORM config visible in inventory)
•No evidence of authentication or authorization implementation
•No evidence of input validation or error handling patterns

Recommendations

Add API documentation (OpenAPI/Swagger) to PaymentService and ProductCatalog +6

PaymentService and ProductCatalog appear to be service-oriented repos but no API documentation is detected; adding Swagger would demonstrate API design competency

Frontend 10Confidence25% · Low

Evidence

PhysioApp name suggests a possible mobile or web application but no frontend framework detected in inventory
No repository lists a frontend language (JavaScript, TypeScript, HTML/CSS) as primary language

Missing

•No evidence of any frontend framework (React, Angular, Vue, etc.)
•No evidence of CSS architecture or responsive design
•No evidence of component-based UI development
•No evidence of frontend build tooling

Recommendations

If PhysioApp has a frontend, document the UI technology stack in its README +3

PhysioApp is the only repo name suggesting a UI but no frontend technology is detectable from inventory data; clarifying the stack would help assess frontend capability

Code Quality 25Confidence25% · Low

Evidence

Repository names use clear, descriptive naming (PaymentService, ProductCatalog, ParkingLot) suggesting some naming discipline
Multiple repos have README files indicating basic project structure awareness

Missing

•No code-level evidence available (no file structure, no function sizes, no type annotations visible from inventory)
•No evidence of linting or code formatting tools (no .editorconfig, checkstyle, or spotless config detected)
•No evidence of error handling patterns
•No evidence of DRY principle application or utility reuse

Recommendations

Add Checkstyle or Spotless to Java projects for automated code quality enforcement +4

No code quality tooling detected in any of the 6 Java repos (PhysioApp, PaymentService, ProductCatalog, TicTacToe, ParkingLot, BookMyShow); adding static analysis would demonstrate quality discipline

Testing 5Confidence40% · Low

Evidence

Zero test files or test directories detected across all 7 repositories
No testing frameworks (JUnit, TestNG, Mockito) visible in any repo inventory
No CI configuration that could run tests detected in any repository

Missing

•Unit tests in all repositories
•Integration tests for service repos (PaymentService, ProductCatalog)
•Edge-case testing for logic-heavy repos (TicTacToe, ParkingLot, BookMyShow)
•Any form of automated test execution

Recommendations

Add JUnit 5 tests to ParkingLot starting with core domain logic +10

ParkingLot is a logic-focused repo where unit tests would be straightforward to add and would demonstrate testing competency; zero tests across all repos is the most critical gap

Add test step to GitHub Actions workflow once CI is set up +5

Even if tests are added, without CI they may not be executed; PaymentService and ProductCatalog should have automated test runs on push

Security 15Confidence30% · Low

Evidence

No evidence of committed secrets in repository metadata (no .env files flagged in inventory)
No authentication implementation visible to assess auth quality
No dependency files visible to check for known CVEs

Missing

•No evidence of input validation or sanitization in any repo
•No evidence of auth implementation in PaymentService or ProductCatalog despite service-oriented names
•No evidence of secrets management (no .env.example, no vault integration)
•No evidence of dependency scanning (no Dependabot or Snyk config detected)

Recommendations

Enable Dependabot alerts for all Java repositories +4

No dependency scanning detected across PhysioApp, PaymentService, ProductCatalog, TicTacToe, ParkingLot, BookMyShow; enabling Dependabot is a low-effort security improvement

Add input validation documentation to PaymentService and ProductCatalog +3

PaymentService and ProductCatalog are service repos where input validation is critical but no evidence of validation patterns exists

DevOps 8Confidence35% · Low

Evidence

No CI/CD pipeline files detected in any of the 7 repositories
No Dockerfile or docker-compose files detected in any repository
No infrastructure-as-code files (Terraform, CloudFormation) detected
No monitoring or logging configuration visible

Missing

•CI/CD pipelines (GitHub Actions, Jenkins, GitLab CI)
•Containerization (Dockerfiles)
•Environment separation (dev/staging/prod configs)
•Monitoring/logging hooks (no Logback, Log4j config detected)

Recommendations

Create a GitHub Actions workflow for BookMyShow that builds and tests the Java project +7

BookMyShow has no CI/CD; adding a simple Maven build workflow would be the highest-impact DevOps improvement and demonstrate deployment readiness

Add a Dockerfile to PaymentService for containerized deployment +5

PaymentService appears to be a backend service with no containerization; adding a Dockerfile would show deployment awareness

Documentation 30Confidence35% · Low

Evidence

All 6 project repositories have README files (PhysioApp, PaymentService, ProductCatalog, TicTacToe, ParkingLot, BookMyShow)
G-dharan/G-dharan has a README with description 'Config files for my GitHub profile'
G-dharan/G-dharan has topics 'config, github-config' providing context

Missing

•No evidence of README quality (setup instructions, architecture docs, usage examples) — READMEs exist but content quality unknown
•No API documentation detected in any repo
•No inline documentation patterns visible
•No changelogs or versioning discipline in any repository
•No topics or descriptions on 5 of 7 repos (PhysioApp, PaymentService, ProductCatalog, TicTacToe, ParkingLot, BookMyShow)

Recommendations

Expand README files with setup instructions, prerequisites, and usage examples +5

READMEs exist in all repos but quality is unknown; adding working setup instructions to PaymentService and BookMyShow would improve documentation scores significantly

Add topics and descriptions to all project repositories +2

5 of 7 repos (PhysioApp, PaymentService, ProductCatalog, TicTacToe, ParkingLot, BookMyShow) lack topics and descriptions, reducing discoverability

Maintainability 20Confidence25% · Low

Evidence

No commit history visible in inventory data to assess commit message quality
No PR history visible to assess PR discipline
No evidence of refactoring over time (no branch structure visible)
Issues enabled on 6 of 7 repos suggesting some awareness of issue tracking

Missing

•No evidence of meaningful commit messages vs 'fix' or 'wip'
•No evidence of small, reviewable PRs
•No evidence of refactoring or code improvement over time
•No evidence of dead code removal or cleanup

Recommendations

Adopt conventional commit messages across all repositories +3

Commit message quality cannot be assessed from inventory data but is a common gap; applying conventional commits to BookMyShow and ParkingLot would improve maintainability signals

Use issues and PRs for tracking changes rather than committing directly to main +4

Issues are enabled on 6 repos but no PR evidence is visible; using PRs for PaymentService and ProductCatalog changes would demonstrate review discipline

Complexity & Judgment 25Confidence20% · Low

Evidence

BookMyShow and ParkingLot represent reasonably complex problem domains beyond simple tutorials
PaymentService and ProductCatalog suggest awareness of service-oriented architecture patterns
TicTacToe is appropriately scoped for a learning project — not over-engineered

Missing

•No evidence of tradeoff documentation or architectural decision records in any repo
•No evidence of choosing appropriate libraries vs hand-rolling solutions
•No evidence of right-sizing solutions (could be over or under-engineering — cannot determine from inventory)
•No evidence of original problem-solving vs following tutorials

Recommendations

Add architectural decision records (ADRs) to BookMyShow explaining key design choices +4

BookMyShow is the most complex repo but no design rationale is visible; adding ADRs would demonstrate judgment and tradeoff awareness, improving this hard-to-assess axis

G-dharan/PaymentService28

Estimated Repository Score

Architecture

Documentation

Testing

Deployment

Security

Complexity

Maintainability

Strengths

Service-oriented naming suggests awareness of microservice patterns · Has a README file · Issues enabled for bug tracking · Payment domain is a non-trivial backend problem space

Weaknesses

No tests detected for a service that handles payments — critical gap · No API documentation (Swagger/OpenAPI) detected · No authentication or input validation evidence for a payment service · No Dockerfile or CI/CD for deployment readiness · No license specified

G-dharan/G-dharan45

Estimated Repository Score

Architecture

Documentation

Testing

Deployment

Security

Complexity

Maintainability

Strengths

Has a clear description: 'Config files for my GitHub profile' · Uses appropriate topics: 'config, github-config' · Has a README file · Appropriately scoped — does not over-engineer a profile config repo

Weaknesses

No license specified · Issues disabled — though appropriate for a config repo · No language detected suggesting minimal content

G-dharan/ProductCatalog28

Estimated Repository Score

Architecture

Documentation

Testing

Deployment

Security

Complexity

Maintainability

Strengths

Service-oriented naming suggests awareness of backend service patterns · Has a README file · Issues enabled for bug tracking · Product catalog is a standard backend domain showing domain awareness

Weaknesses

No tests detected for catalog logic · No API documentation detected · No Dockerfile or CI/CD pipeline · No license specified · No topics or description providing context

G-dharan/TicTacToe22

Estimated Repository Score

Architecture

Documentation

Testing

Deployment

Security

Complexity

Maintainability

Strengths

Appropriately simple project for learning — TicTacToe is a good beginner exercise · Has a README file · Issues enabled

Weaknesses

No tests detected — TicTacToe game logic is highly testable making this a missed opportunity · No CI/CD pipeline · No license specified · No topics or description

G-dharan/ParkingLot30

Estimated Repository Score

Architecture

Documentation

Testing

Deployment

Security

Complexity

Maintainability

Strengths

ParkingLot is a well-known system design problem showing awareness of design patterns · Has a README file · Issues enabled · Domain involves non-trivial state management (spots, vehicles, tickets)

Weaknesses

No tests detected for parking logic (spot allocation, fee calculation) · No CI/CD pipeline or Dockerfile · No license specified · No topics or description

G-dharan/BookMyShow32

Estimated Repository Score

Architecture

Documentation

Testing

Deployment

Security

Complexity

Maintainability

Strengths

BookMyShow is a complex domain involving seat booking, concurrency, and transactions — shows ambition · Has a README file · Issues enabled · Most complex problem domain among all repositories

Weaknesses

No tests detected for booking logic — critical for a system involving seat reservations and concurrency · No CI/CD pipeline or Dockerfile · No license specified · No topics or description · No evidence of concurrency handling or transaction management documentation