© 2026 GitRating by Mozen.in. All rights reserved.
R.Abisheik — Engineering Score: 32/100 (Junior) | GitRating
Public Profile
R.Abisheik Full-Stack Developer | MERN Specialist | Coding in the graveyard
70 Repos
169 Followers
11 Following
32
out of 100
Junior
Confidence 55% · Medium
Language Capabilities
Most used overall JavaScript 57% 2 languages coded
Overall Summary
Developer exhibits high repository volume (70 repos) but suffers from a low signal-to-noise ratio. While claiming MERN specialization and active development, most projects lack READMEs, tests, or meaningful engagement (stars/forks). Evidence suggests a mix of utility tools (VS Code extension, automation scripts) and placeholder repositories.
Fahh (VS Code extension) demonstrates practical utility and developer tooling awareness. linkedin-daily-automation shows understanding of CI/CD workflows via GitHub Actions. javascript-interview-questions repository provides a useful reference resource. Category Breakdown — evidence for every score
Frontend 35 Confidence 60% · Medium
Evidence
codebyabi-portfolio (CSS) indicates basic styling capability. next-blog (JavaScript) suggests familiarity with Next.js stack. Missing
• No evidence of component libraries (React, Vue) or modern CSS frameworks (Tailwind, Styled-components). • No responsive design evidence detected. Repository Intelligence
Estimated Repository Score
Know your own score. Connect GitHub and get your explainable Engineering Score in 60 seconds. Free.
Get your GitRating
• Test-Repo is a placeholder repository with zero value, indicating potential repo hoarding.
• 50% of listed repositories lack README files, making them unusable for collaboration.
• No evidence of automated testing frameworks (Jest, Mocha, etc.) detected in any repository.
• Athena-AI and github-career-analyzer lack code evidence to support the ambitious claims in descriptions. +5 Archive or Delete Placeholder Repositories
Repositories like 'Test-Repo' and 'batch-4' clutter the profile and lower perceived professionalism. Archiving them improves the signal-to-noise ratio.
+10 Standardize README Documentation
Repositories like 'MERN_TUTOR_1', 'nodemailer', and 'app' lack READMEs, preventing others from understanding the project's purpose or usage.
+15 Implement Automated Testing
No test files were detected in any repository. Adding unit tests to projects like 'Fahh' or 'linkedin-daily-automation' is critical for code quality.
+5 Refactor 'Athena-AI' and 'github-career-analyzer'
These repositories have high complexity descriptions but low star counts and no visible code structure. They need substantial code implementation to be viable.
Add Component Architecture +5 Projects like 'next-blog' should be refactored into modular components rather than monolithic files.
Backend 40 Confidence 55% · Medium
Evidence
MERN_TUTOR_1 (JavaScript) claims MERN stack specialization. nodemailer (TypeScript) indicates server-side email handling knowledge. Missing
• No API route definitions or server logic visible in metadata. • No database schema or ORM usage detected in listed repos. Recommendations
Implement REST or GraphQL APIs +5 MERN claims require visible API endpoints and database connectivity, which is currently absent from the repository evidence.
DevOps 20 Confidence 70% · Medium
Evidence
linkedin-daily-automation description mentions GitHub Actions cron jobs. Missing
• No Dockerfiles detected. • No Kubernetes manifests. • No CI/CD pipeline configurations (e.g., .github/workflows) found in other repos. Recommendations
Containerize Applications +5 Adding Dockerfiles to backend projects like 'nodemailer' would demonstrate modern deployment practices.
Testing 10 Confidence 100% · High
Missing
• No test files (.spec.js, .test.ts, __tests__) detected in any repository. • No test runners mentioned in package.json (inferred from lack of evidence). Recommendations
Add Unit and Integration Tests +15 Zero test coverage is a critical gap for a 'Full-Stack Developer'.
Security 15 Confidence 70% · Medium
Missing
• No evidence of environment variable management (.env files or secrets management). • No input validation libraries detected. • No dependency scanning reports visible. Recommendations
Secure Environment Variables +5 Backend projects like 'nodemailer' must use .env files to store API keys securely.
Architecture 25 Confidence 50% · Medium
Evidence
Full-stack repository describes a roadmap, suggesting architectural planning. Missing
• No folder structures visible (e.g., src/, components/, lib/). • Monolithic code structure suspected in low-star projects. Recommendations
Adopt Modular Project Structure +5 Projects like 'app' and 'newRealEstate' likely suffer from spaghetti code due to lack of architectural planning.
Documentation 30 Confidence 60% · Medium
Evidence
Full-stack has a README. Fahh has a README. Athena-AI has a README. Missing
• 50% of repos lack READMEs. • No inline code comments or JSDoc/TSDoc detected. • No contributing guides. Recommendations
Write Comprehensive READMEs +10 Repositories like 'MERN_TUTOR_1' and 'nodemailer' are unusable without installation and usage instructions.
10
Strengths
Provides a roadmap for Full-stack development.
Weaknesses
No code implementation detected, only a roadmap. · N/A language indicates lack of technical stack definition.
Estimated Repository Score
Strengths
TypeScript implementation shows type safety awareness. · Has README.
Weaknesses
No topics listed, making it hard to find. · Low stars indicate lack of adoption or visibility.
Estimated Repository Score
Strengths
Practical utility: VS Code extension for error sound alerts. · Good README explaining the purpose.
Weaknesses
No testing detected. · No deployment configuration (VSIX packaging not confirmed).
Estimated Repository Score
Strengths
Claims MERN stack specialization.
Weaknesses
No README. · No visible code structure. · Low stars suggest it is a tutorial or incomplete code.
Estimated Repository Score
Strengths
Uses TypeScript for type safety.
Weaknesses
No README. · Likely boilerplate code. · No security best practices visible (e.g., no .env example).
Estimated Repository Score
Strengths
Practical automation script using GitHub Actions. · Good description of functionality.
Weaknesses
No test files. · No Dockerfile for containerization. · Security risk: API keys should be handled securely.
Estimated Repository Score
Strengths
Uses TypeScript. · Has README.
Weaknesses
Forked repository (different owner). · Low activity. · No evidence of RAG implementation in code.
Estimated Repository Score
Weaknesses
No README. · No description. · Low stars.
Estimated Repository Score
Weaknesses
N/A language. · Likely a profile or organizational repository.
Estimated Repository Score
Strengths
Interesting concept.
Weaknesses
No README. · No code visible. · Low stars.
Estimated Repository Score
Strengths
Provides a list of 1000 questions. · Has README.
Weaknesses
Static content, no code. · No categorization or difficulty levels.
Estimated Repository Score
Weaknesses
No README. · No description. · Academic assignment likely.
Estimated Repository Score
Strengths
Has README. · Uses TypeScript.
Weaknesses
No topics. · No code visible. · Low stars.
Estimated Repository Score
Strengths
Educational topic.
Weaknesses
No README. · No implementation code.
Estimated Repository Score
Strengths
MIT License. · Ambitious description.
Weaknesses
No topics. · No code visible. · Low stars.
Estimated Repository Score
Weaknesses
No README. · No code. · Irrelevant to software engineering.
Estimated Repository Score
Weaknesses
Explicitly a test repository. · No value add.
Estimated Repository Score
Weaknesses
No README. · Different owner. · No code.
Estimated Repository Score
Weaknesses
No topics. · No code.
Estimated Repository Score
Strengths
CSS implementation. · Has issues (active).
Weaknesses
No README. · 1 open issue. · No responsive design evidence.
Estimated Repository Score
Weaknesses
No README. · Description: 'for my class students'. · No value for public.
Estimated Repository Score
Strengths
Uses JavaScript.
Weaknesses
No README. · No code visible. · Likely incomplete payment integration.
Estimated Repository Score
Weaknesses
No README. · Generic name. · No code.
Estimated Repository Score
Strengths
Uses JavaScript.
Weaknesses
No README. · No code visible. · Generic name.
Estimated Repository Score
Weaknesses
No README. · No code. · Python language but no implementation.
Estimated Repository Score
Strengths
Uses JavaScript.
Weaknesses
No README. · No code visible.
Estimated Repository Score
Weaknesses
No README. · No code. · Generic name.
Estimated Repository Score
Weaknesses
No README. · No code. · Generic name.
Estimated Repository Score
Strengths
Uses JavaScript (likely Next.js based on name).
Weaknesses
No README. · No code visible. · No topics.
Estimated Repository Score
Strengths
Has README. · Uses TypeScript.
Weaknesses
No topics. · No code visible. · Ambitious claim.
