Public Profile

JAHANGEER I

full stack developer

26Repos

8Followers

4Following

out of 100

Junior

Confidence35% · Low

Skill Radar

Language Capabilities

Most used overallTypeScript35%8 languages coded

TypeScript

35%

CSS

30%

PHP

14%

HTML

12%

JavaScript

Hack

Shell

Overall Summary

Jahangeer demonstrates activity across full-stack technologies (TypeScript, Java, Python) but exhibits strong patterns of tutorial-following and assignment completion rather than independent engineering. The absence of tests, licenses, topics, and stars across 26 repositories, combined with a high volume of missing READMEs, indicates a lack of production-readiness and project ownership.

Strengths

Exposure to a diverse set of technologies including TypeScript (futureblink_ai, nxtace-be), Java (zoho, acet), and Python (scrapper)
Attempts full-stack architecture by splitting frontend and backend into separate repositories (nxtace-fe/nxtace-be, low-code-fe/low-code-be)
Uses TypeScript for modern backend and frontend development (tm-auth, ulnlabs-shortsgen-fe)

Missing

Category Breakdown — evidence for every score

Architecture 30Confidence40% · Low

Evidence

Separation of frontend and backend into distinct repos (nxtace-fe, nxtace-be, low-code-fe, low-code-be)
Presence of an express-mvc repository suggesting an attempt at structured backend design
Microservice-like split seen in CRM projects (crm-auth-be, crm-user-be, crm-gateway-be)

Missing

Repository Intelligence

jahangeer-dev/futureblink_ai30

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

•Zero test coverage detected across all 26 repositories, indicating a lack of verification and reliability practices
•Missing READMEs in 12 out of 26 repositories (e.g., frontend-akn, isco_task, crm-auth-be), making projects impossible to onboard or evaluate
•No CI/CD pipelines, Dockerfiles, or deployment configurations detected in any repository
•Forked repositories like axios are present but show zero contribution or differentiation from the upstream source
•No licenses declared in 24 out of 26 repositories, restricting legal reuse and indicating a lack of open-source maturity

Recommendations

+10

Add integration and unit tests to backend services

No tests are detected in any repository. Adding tests to nxtace-be or tm-auth would immediately improve reliability scores and demonstrate professional engineering standards.

Write comprehensive READMEs for all project repositories

12 repositories like crm-user-be and low-code-be lack a README. Documenting setup, architecture, and usage is critical for maintainability and collaboration.

Introduce CI/CD and containerization

No Dockerfiles or CI configs detected. Adding a basic GitHub Actions workflow to express-mvc or nxtace-be would demonstrate deployment readiness.

Remove empty fork repositories and test placeholders

Repositories like axios and test add noise to the profile without demonstrating skill. Cleaning these up improves the signal-to-noise ratio of the portfolio.

Backend 35Confidence40% · Low

Evidence

TypeScript used for backend services (tm-auth, nxtace-be, crm-gateway-be)
Dedicated authentication service (tm-auth) indicates familiarity with auth concepts
Python scrapper repository shows basic scripting capability

Missing

•API documentation (Swagger/OpenAPI)
•Database usage patterns and ORM implementation details
•Evidence of proper input validation or sanitization

Recommendations

Add input validation to API endpoints +6

No validation libraries or patterns detected in tm-auth or nxtace-be; this is a critical security and reliability gap.

Frontend 30Confidence35% · Low

Evidence

TypeScript used in frontend projects (ulnlabs-shortsgen-fe, nxtace-fe)
HTML/CSS projects (isco, vigovia) show foundational web development skills

Missing

•Component quality assessment (reusability, prop typing)
•CSS architecture (Tailwind, CSS-in-JS, or modular CSS)
•Responsive design patterns

Recommendations

Modernize CSS architecture in frontend projects +4

isco_task is CSS-based but lacks context. Using a modern framework like Tailwind in nxtace-fe would demonstrate frontend maturity.

Code Quality 25Confidence30% · Low

Evidence

Use of TypeScript across multiple projects suggests an attempt at type safety (futureblink_ai, tm-auth)
express-mvc repo implies an effort to structure code logically

Missing

•Linting configurations (ESLint, Prettier)
•Evidence of DRY principles or shared utilities
•Error handling patterns (no try/catch or error middleware visible in metadata)

Recommendations

Enforce strict ESLint and Prettier rules +5

No linting detected. Adding ESLint to futureblink_ai and nxtace-be would instantly improve code consistency and catch type errors.

Testing 0Confidence90% · High

Evidence

Zero test files or testing frameworks detected in the metadata of any of the 26 repositories
No CI configurations present to run tests

Missing

•Unit tests
•Integration tests
•End-to-end tests

Recommendations

Add Jest tests to backend services +15

Testing is completely absent. Starting with unit tests for express-mvc or tm-auth is the highest-impact improvement available.

Security 20Confidence35% · Low

Evidence

tm-auth repository exists, indicating some focus on authentication
No committed secrets detected in repository metadata (though deep scanning is needed)

Missing

•Evidence of proper password hashing (bcrypt/argon2)
•Input validation and sanitization
•Dependency vulnerability scanning (Dependabot not enabled)

Recommendations

Enable Dependabot and implement input validation +8

No dependency hygiene detected. Enabling Dependabot on tm-auth and adding validation libraries to nxtace-be would mitigate common vulnerabilities.

DevOps 5Confidence50% · Medium

Evidence

No Dockerfiles detected in any repository
No CI/CD pipeline files (e.g., .github/workflows) detected

Missing

•Docker/containerization
•CI/CD pipelines
•Environment separation (dev/staging/prod)
•Monitoring and logging hooks

Recommendations

Create a basic GitHub Actions CI workflow +10

No CI/CD detected. Adding a workflow to express-mvc that runs linting and tests would establish a baseline for DevOps maturity.

Documentation 20Confidence80% · High

Evidence

14 out of 26 repositories have a README (e.g., futureblink_ai, copyflow, scrapper)
12 out of 26 repositories completely lack a README (e.g., frontend-akn, isco_task, crm-auth-be)

Missing

•API documentation (Swagger/OpenAPI)
•Inline architecture comments
•Changelog and versioning discipline

Recommendations

Write detailed READMEs for all CRM backend repos +6

crm-auth-be, crm-user-be, and crm-gateway-be lack READMEs. Documenting these is essential for understanding the microservice architecture.

Maintainability 15Confidence40% · Low

Evidence

No topics or licenses used to organize and clarify repository usage
Only 2 repositories have licenses (copyflow, axios)

Missing

•Commit message quality analysis (unable to verify from metadata)
•PR discipline and code review evidence
•Refactoring evidence over time

Recommendations

Add MIT licenses and topics to all original repositories +3

24 repos lack licenses. Adding licenses and topics to projects like futureblink_ai improves discoverability and professional presentation.

Complexity & Judgment 25Confidence20% · Low

Evidence

Repository names like fullstack-intern-task and isco_task suggest these are assignment projects rather than original problem-solving
Splitting a CRM into 3 microservices (auth, user, gateway) might be over-engineering for a personal project with 0 stars and no deployment infrastructure

Missing

•Evidence of tradeoff analysis or architectural decision records
•Original problem-solving vs tutorial/assignment completion

Recommendations

Consolidate CRM microservices into a monolith +4

Maintaining crm-auth-be, crm-user-be, and crm-gateway-be separately without CI/CD or deployment infrastructure adds unnecessary complexity. A monolithic approach in express-mvc would show better judgment.