Developer Profile

Aung Myat Moe

@theaungmyatmoe

Yangon, Myanmar

GitHub

Impact Score Overview

Developer Impact & Statistics

Final Score

44 / 100Raw: 201.00

Repository Score

31 / 100Raw: 44.00

PR Score

56 / 100Raw: 381.00

Contribution Score

49 / 100Raw: 95.00

Score Weight Distribution

finalScore = repoScore * 0.45 + prScore * 0.45 + contributionScore * 0.10

Repository Score (45%)10% of final signal

Pull Request Score (45%)85% of final signal

Contribution Score (10%)5% of final signal

Top Work

Top Work & Highlights

Top Repositories

Most impactful repositories and pull requests

#1panify

stars19

forks9

TypeScript 7300%JavaScript 2700%

Score

#2aungmyatmoe.me

stars17

forks2

MDX 6700%JavaScript 3300%

Score

#3wuttyi-lang

stars12

forks3

JavaScript 10000%

Score

Top Pull Requests

Most impactful repositories and pull requests

#1Langs:Myanmar(ဗမာစာ) unicode (Standard) and Zawgyi (Use By Some Devic…

in Acode-Foundation/Acode

stars on the PR repository6804

+335/-2

JavaScript 6000%Java 1700%TypeScript 1500%

Score

#2:fire: build: add profile Aung Myat Moe

in myanmar-software-engineers/myanmar-software-engineers.github.io

stars on the PR repository128

+183/-0

TypeScript 6000%MDX 3700%SCSS 200%

Score

#3doc: create CODE_OF_CONDUCT.md

in myanmar-software-engineers/myanmar-software-engineers.github.io

stars on the PR repository128

+128/-0

TypeScript 6000%MDX 3700%SCSS 200%

Score

Community Contributions

comments

#1Issue

Hydration failed because the initial UI does not match what was rendered on the server.Hydration failed because the initial UI does not match what was rendered on the server.Hydration failed because the initial UI does not match what was rendered on the server.

vercel/next.js

stars142088

comments16

Score

#2Issue

Partial Hydrtion failed with Error Boundary

vercel/next.js

stars142088

comments11

Score

#3Issue

[Bug] satisfies operator is not satify in compile time

microsoft/TypeScript

stars110886

comments6

Score

Scoring Transparency

▼

Repositories analyzed

Pull requests analyzed

116

Merged external PRs counted

116

Own-repo PRs ignored

Unmerged PRs ignored

Unique external repositories

Issues analyzed

100

External issues counted

100

Discussions analyzed

External discussions counted

How this score was calculated

View the full scoring methodology with formulas, penalties, and step-by-step flow.

View full methodology