Developer Profile

Thomas Bocek

@tbocek

Zurich, Switzerland

GitHub

Impact Score Overview

Developer Impact & Statistics

Final Score

63 / 100Raw: 507.00

Repository Score

54 / 100Raw: 118.00

PR Score

77 / 100Raw: 995.00

Contribution Score

39 / 100Raw: 64.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%)88% of final signal

Contribution Score (10%)2% of final signal

Top Work

Top Work & Highlights

Top Repositories

Most impactful repositories and pull requests

#1dvorak

stars87

forks26

C 9700%Makefile 300%

Score

#2preveltekit

stars38

forks1

Go 8000%JavaScript 1200%Shell 600%

Score

#3llm-local-web-search

stars10

forks2

JavaScript 9000%HTML 900%

Score

Top Pull Requests

Most impactful repositories and pull requests

#1Signature Malleability:

in OpenZeppelin/openzeppelin-contracts

stars on the PR repository27231

+66/-35

Solidity 5500%JavaScript 4200%TypeScript 200%

104

Score

#2Negative numbers not properly converted in ABI encoding

in ethereum/go-ethereum

stars on the PR repository51328

+10/-64

Go 8600%C 1100%JavaScript 200%

103

Score

#3Add the possibility to connect via ssh to a remote docker node.

in moncho/dry

stars on the PR repository3275

+168/-72

Go 9900%Shell 100%

Score

Community Contributions

comments

#1Issue

NioDatagramWorker Issues

netty/netty

stars35046

comments13

Score

#2Issue

3.3TB disk usage?

erigontech/erigon

stars3582

comments16

Score

#3Issue

channelFuture.addListener() throws exception if channel is closed

netty/netty

stars35046

comments7

Score

Scoring Transparency

▼

Repositories analyzed

Pull requests analyzed

Merged external PRs counted

Own-repo PRs ignored

Unmerged PRs ignored

Unique external repositories

Issues analyzed

External issues counted

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