Developer Profile

Hiroshi Miura

@miurahr

Kita-city, Tokyo, Japan

GitHub

Impact Score Overview

Developer Impact & Statistics

Final Score

74 / 100Raw: 964.00

Repository Score

71 / 100Raw: 249.00

PR Score

86 / 100Raw: 1883.00

Contribution Score

32 / 100Raw: 46.00

Score Weight Distribution

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

Repository Score (45%)12% of final signal

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

Contribution Score (10%)0% of final signal

Top Work

Top Work & Highlights

Top Repositories

Most impactful repositories and pull requests

#1aqtinstall

stars1340

forks118

watchers17

Python55%HTML35%C++7%

Score

#2py7zr

stars558

forks95

watchers10

Python98%Shell2%

Score

#3pykakasi

stars464

forks56

watchers3

Python100%

Score

Top Pull Requests

Most impactful repositories and pull requests

#1Add Japanese translation

in vnotex/vnote

stars on the PR repository13011

+3561/-1

C++62%JavaScript31%CSS3%

104

Score

#2CMake: Improve packaging script

in vnotex/vnote

stars on the PR repository13011

+128/-158

C++62%JavaScript31%CSS3%

104

Score

#3Introduce GitHub actions test with CMake

in vnotex/vnote

stars on the PR repository13011

+364/-158

C++62%JavaScript31%CSS3%

104

Score

Community Contributions

Most impactful public issues and discussions

#1Issue

machine_info['cpu'] become always unknown

ionelmc/pytest-benchmark

stars1457

comments8

Score

#2Issue

machine_info['cpu'] become always unknown

ionelmc/pytest-benchmark

stars1457

comments8

Score

#3Issue

Feature request: Support Linux for aarch64

uowuo/abaddon

stars2226

comments5

Score

Scoring Transparency

▼

Repositories analyzed

Pull requests analyzed

300

Merged external PRs counted

300

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