Public Profile

MOHAMMED IMRAN

🎨 UX Designer & Architect | 💻 Full-Stack MERN Developer | 🚀 SaaS & AI-Powered App Developer | ✍️ Content Creator

18Repos

245Followers

18Following

out of 100

Mid-Level

Confidence60% · Medium

Skill Radar

Language Capabilities

Most used overallTypeScript75%5 languages coded

TypeScript

75%

JavaScript

13%

HTML

CSS

TSQL

Overall Summary

MOHAMMED IMRAN demonstrates versatility across the MERN stack, AI tools, and CLI development, with a standout architectural project in 'Kesmo-cli'. However, the portfolio is dominated by tutorial-style collections and simple utility scripts, lacking evidence of production-grade testing, security hardening, or complex system design.

Strengths

Architectural intent shown in 'Kesmo-cli' which utilizes TypeScript and multi-provider LLM agents.
Broad technical stack coverage including MERN, AI (Gemini/OpenRouter), and CLI tools.
Active content creation evident in 'Instagram-Code-Bites' and '100-Web-Projects'.

Missing

Category Breakdown — evidence for every score

Architecture 40Confidence65% · Medium

Evidence

Kesmo-cli demonstrates architectural intent with TypeScript and multi-provider LLM integration.
Binario shows basic separation of concerns with Express endpoints.

Missing

•Evidence of caching, queuing, or rate-limiting in backend repos.
•Complex state management patterns in Frontend repos.

Recommendations

Repository Intelligence

AMOHAMMEDIMRAN/Kesmo-cli60

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

•Lack of evidence for testing frameworks in any repository (e.g., Jest, Cypress).

•Heavy reliance on 'learning purposes' and 'collection' descriptions in repos like '100-Web-Projects' and 'The-API-Vault'.

•No evidence of CI/CD pipelines or Docker deployment readiness in the provided data.

•Security practices are not visible; no evidence of input validation or secure auth in simple API repos like 'Binario'.

Recommendations

Implement automated testing for 'Kesmo-cli'

As the most architecturally significant repo, adding unit and integration tests will validate the multi-provider LLM logic and improve reliability.

Refactor '100-Web-Projects' into a monorepo

Managing 100 separate repositories indicates high maintenance overhead and likely code duplication; a monorepo structure would improve maintainability.

Add CI/CD pipeline to 'Binario' and 'The-API-Vault'

These Node.js/Express APIs lack evidence of automated deployment, increasing the risk of manual errors and inconsistent environments.

Add README to 'React-Masterpieces'

Missing README makes the repository unusable for others and suggests incomplete project documentation.

Design a modular architecture for '100-Web-Projects' +5

The current structure implies a flat list of projects rather than a scalable system.

Backend 30Confidence70% · Medium

Evidence

Binario uses Express.js for string conversion.
The-API-Vault uses Express.js and Node.js.

Missing

•Database schema definitions or ORM usage.
•Authentication middleware or JWT implementation.
•Error handling strategies (e.g., try/catch blocks).

Recommendations

Implement input validation in 'Binario' +4

String-to-binary conversion requires strict input validation to prevent crashes.

Frontend 45Confidence60% · Medium

Evidence

React-Weather-Pro and Dev-Profile-Card use React.
Amazing-Landing-Page uses Bootstrap.

Missing

•Component library usage (e.g., Material UI, Tailwind).
•State management libraries (e.g., Redux, Context API) usage patterns.
•Accessibility (a11y) attributes.

Recommendations

Standardize CSS architecture across Frontend repos +3

Mix of plain CSS and Bootstrap suggests inconsistent styling approaches.

Code Quality 35Confidence55% · Medium

Evidence

Kesmo-cli uses TypeScript for type safety.
npm-logzap uses descriptive function names.

Missing

•ESLint or Prettier configuration files.
•No evidence of 'any' type usage in TS files.
•No evidence of code splitting or lazy loading.

Recommendations

Enforce TypeScript strict mode in 'SummifyAi' +3

Using React + Vite suggests a modern stack; strict typing is essential for AI integration.

Testing 5Confidence90% · High

Evidence

No strong evidence.

Missing

•No test directories (e.g., __tests__, tests) found in any repository.
•No CI scripts running tests (e.g., GitHub Actions workflows).

Recommendations

Add unit tests to 'Kesmo-cli' +8

The CLI logic is complex; testing is critical to ensure LLM agent behavior is correct.

Security 20Confidence80% · High

Evidence

No strong evidence.

Missing

•No evidence of environment variable management (e.g., .env files).
•No evidence of HTTPS enforcement in API repos.
•No evidence of input sanitization to prevent XSS/SQLi.

Recommendations

Implement environment variable management for API keys +5

AI-powered repos like 'Kesmo-cli' and 'SummifyAi' likely require API keys which must not be committed.

DevOps 5Confidence85% · High

Evidence

No strong evidence.

Missing

•No Dockerfiles detected.
•No CI/CD pipelines (GitHub Actions, GitLab CI).
•No deployment links provided in repository descriptions.

Recommendations

Create a Dockerfile for 'The-API-Vault' +4

Standardizing deployment via Docker improves consistency across environments.

Documentation 40Confidence70% · Medium

Evidence

Kesmo-cli has a README.
Binario has a README with endpoints.
Portfolio-Giveway has a README.

Missing

•Inline comments explaining complex logic in 'Kesmo-cli'.
•API documentation (Swagger/OpenAPI) for 'The-API-Vault'.
•Changelog or versioning history.

Recommendations

Add inline comments to 'Kesmo-cli' agents +3

Multi-provider LLM integration logic is complex and benefits from documentation.

Maintainability 30Confidence65% · Medium

Evidence

Active contribution to multiple repos.

Missing

•Consistent commit message formatting.
•Evidence of refactoring old code.
•No dead code removal in '100-Web-Projects'.

Recommendations

Standardize commit messages +3

Improves traceability and code review efficiency.

Complexity & Judgment 30Confidence40% · Low

Evidence

Kesmo-cli attempts a complex multi-agent system.

Missing

•Evidence of trade-off analysis in code comments.
•Comparison with industry-standard libraries (e.g., LangChain).
•Reasoning for choosing specific tech stacks.

Recommendations

Document architectural decisions in 'Kesmo-cli' +3

To demonstrate understanding of the trade-offs involved in building a custom AI CLI.

Strengths

Uses TypeScript for type safety. · Implements multi-provider LLM integration (OpenAI, Claude, etc.). · Focuses on code quality analysis and security.

Weaknesses

No evidence of testing infrastructure. · Likely lacks CI/CD automation. · Security handling of API keys is unknown.

AMOHAMMEDIMRAN/antigravity-claude-proxy45

Estimated Repository Score

Architecture

Documentation

Testing

Deployment

Security

Complexity

Maintainability

Strengths

MIT License indicates open-source intent. · README provides basic setup instructions.

Weaknesses

No evidence of input validation. · No testing detected. · Proxy logic complexity unknown without code inspection.

AMOHAMMEDIMRAN/Portfolio-Giveway35

Estimated Repository Score

Architecture

Documentation

Testing

Deployment

Security

Complexity

Maintainability

Strengths

Designed for customization. · Responsive design focus.

Weaknesses

Template nature suggests lack of unique architecture. · No evidence of testing or deployment.

AMOHAMMEDIMRAN/100-Web-Projects15

Estimated Repository Score

Architecture

Documentation

Testing

Deployment

Security

Complexity

Maintainability

Strengths

Covers a wide range of frontend concepts.

Weaknesses

Collection of 100 projects indicates low depth per project. · No README for many individual projects. · High maintenance overhead.

AMOHAMMEDIMRAN/React-Masterpieces20

Estimated Repository Score

Architecture

Documentation

Testing

Deployment

Security

Complexity

Maintainability

Strengths

Uses React framework.

Weaknesses

No README provided. · Likely tutorial-based code. · No evidence of testing.

AMOHAMMEDIMRAN/Dev-Profile-Card25

Estimated Repository Score

Architecture

Documentation

Testing

Deployment

Security

Complexity

Maintainability

Strengths

Responsive design. · Clean component structure implied.

Weaknesses

Very low star count suggests limited adoption. · No testing evidence.

AMOHAMMEDIMRAN/Binario30

Estimated Repository Score

Architecture

Documentation

Testing

Deployment

Security

Complexity

Maintainability

Strengths

Express.js API structure. · Documented endpoints.

Weaknesses

Simple logic implies lack of complexity. · No evidence of security middleware.

Jia-codedev/Identra-FrontEnd25

Estimated Repository Score

Architecture

Documentation

Testing

Deployment

Security

Complexity

Maintainability

Strengths

Uses TypeScript.

Weaknesses

Low star count. · Forked/External repo context unclear.

AMOHAMMEDIMRAN/The-API-Vault30

Estimated Repository Score

Architecture

Documentation

Testing

Deployment

Security

Complexity

Maintainability

Strengths

Express.js backend. · JSON data format focus.

Weaknesses

Collection style suggests lack of depth. · No evidence of testing.

AMOHAMMEDIMRAN/React-Weather-Pro30

Estimated Repository Score

Architecture

Documentation

Testing

Deployment

Security

Complexity

Maintainability

Strengths

Uses React and OpenWeatherMap API. · Responsive design.

Weaknesses

Simple API integration logic. · No error handling for API failures.

AMOHAMMEDIMRAN/VSCode-setup0

Estimated Repository Score

Architecture

Documentation

Testing

Deployment

Security

Complexity

Maintainability

Strengths

Configuration files documented.

Weaknesses

Not a code repository; purely configuration. · No engineering value in this context.

AMOHAMMEDIMRAN/Amazing-Landing-Page20

Estimated Repository Score

Architecture

Documentation

Testing

Deployment

Security

Complexity

Maintainability

Strengths

Uses Bootstrap. · Responsive layout.

Weaknesses

No README. · Likely static page with minimal logic.

AMOHAMMEDIMRAN/Instagram-Code-Bites20

Estimated Repository Score

Architecture

Documentation

Testing

Deployment

Security

Complexity

Maintainability

Strengths

Content-focused. · Covers multiple languages.

Weaknesses

No README. · Snippets imply low complexity. · Not a deployable application.

AMOHAMMEDIMRAN/Diverse-JavaScript-Projects20

Estimated Repository Score

Architecture

Documentation

Testing

Deployment

Security

Complexity

Maintainability

Strengths

Demonstrates variety of JS concepts.

Weaknesses

No README. · Collection style.

AMOHAMMEDIMRAN/Biosta-AI-Powered-Instagram-Bio-Generator40

Estimated Repository Score

Architecture

Documentation

Testing

Deployment

Security

Complexity

Maintainability

Strengths

AI-powered functionality. · Uses modern web stack (implied).

Weaknesses

No evidence of API key security. · No testing. · Simple prompt logic likely.

Anu-Pro-Dev/identra-visitor-management25

Estimated Repository Score

Architecture

Documentation

Testing

Deployment

Security

Complexity

Maintainability

Strengths

TypeScript usage. · Visitor management domain logic.

Weaknesses

0 stars. · No evidence of testing or deployment.

AMOHAMMEDIMRAN/npm-logzap25

Estimated Repository Score

Architecture

Documentation

Testing

Deployment

Security

Complexity

Maintainability

Strengths

Solves a specific logging problem. · Simple API.

Weaknesses

Minimalistic utility implies low complexity. · No testing.

AMOHAMMEDIMRAN/SummifyAi40

Estimated Repository Score

Architecture

Documentation

Testing

Deployment

Security

Complexity

Maintainability

Strengths

Uses React + Vite. · Integrates with Gemini API.

Weaknesses

No evidence of input length limits. · No testing. · API key security unknown.