logo zerocracy

You can get a similar report for your project

This week
⬇
Programmer / Award Reasonw38w39w40w41w42w43w44w45RunPay
@vasilevnstas@vasilevnstas (2 awards)————————+48
@thayorns@thayorns (130 awards)+698+912+356+24+312+130+44—+2638
@titanism0v0@titanism0v0 (6 awards)—+136——————+136
@demach89@demach89 (1 award)—————+24——+24
@opusstudiohq-max@opusstudiohq-max (43 awards)+18+244+104—+112+372+18—+936
@canburakyol@canburakyol (4 awards)—+40+36—————+76
@vova4o@vova4o (1 award)———+20————+20
@macoladik@macoladik (4 awards)—————+44+14—+58
@ghx5t-sol@ghx5t-sol (1 award)——————+20—+20
@akmhatey-ai@akmhatey-ai (1 award)——————+20—+20
@morphqdd@morphqdd (1879 awards)+4180+6920+3512+1064+10220+4154+2002—+35252
@gemshrine@gemshrine (678 awards)+2432+1644+2384+366+1892+470+630—+12404
@twaldin@twaldin (18 awards)—+228+112—————+398
@comradexlight@comradexlight (1 award)————+18———+18
@renyamamoto2026-cmyk@renyamamoto2026-cmyk (67 awards)—————+1206——+1206
@erroriakovlev@erroriakovlev (2 awards)—————+36——+36
@yegor256@yegor256 (154 awards)+120+82+40-34+74+120+96—+572-7572
@eugene-chernyshenko@eugene-chernyshenko (1 award)-6———————-6
@williamleewilliam1-star@williamleewilliam1-star (2 awards)————-12———-12
@jasmineabram107-netizen@jasmineabram107-netizen (5 awards)—————+72——+72
@jenningsbrad73-cyber@jenningsbrad73-cyber (1 award)————-8———-8
Total (3002/6090):+7436+10206+6544+1440+12608+6628+2844—+53902

Assessment

The average reward per task (17.2 points) is increasing (R=0.29). The average punishment per task (7.0 points) is decreasing (R=0.13). The average number of builds per week (6361.5) is increasing (R=0.58). The average number of commits per week (91.8) is increasing (R=0.22). The average bugs accepted per month (303.0) is increasing (R=0.74). The average monthly punishment (258 points) is increasing (R=0.13). The average monthly wage (17.5 points) is increasing (R=0.56). The average issue cycle time (1w3d) is staying still. The average pull cycle time (1w2d) is increasing (R=0.17). The average number of releases per month (3.8) is decreasing (R=-0.41). The average monthly turnover (16.0 developers) is increasing (R=0.81). The average weekly cost of HoC (1.19 points) is decreasing (R=-0.50). The average monthly zents/points ratio (0.85) is decreasing (R=0.31).

Assessment

The average reward per task (17.2 points) is increasing (R=0.29). The average punishment per task (7.0 points) is decreasing (R=0.12). The average number of builds per week (6361.5) is increasing (R=0.58). The average number of commits per week (91.8) is increasing (R=0.22). The average bugs accepted per month (303.0) is increasing (R=0.74). The average monthly punishment (258 points) is increasing (R=0.14). The average monthly wage (17.5 points) is increasing (R=0.60). The average issue cycle time (1w3d) is staying still. The average pull cycle time (1w3d) is increasing (R=0.23). The average number of releases per month (3.8) is decreasing (R=-0.41). The average monthly turnover (17.0 developers) is increasing (R=0.85). The average weekly cost of HoC (1.12 points) is decreasing (R=-0.40). The average monthly zents/points ratio (0.85) is decreasing (R=0.27).

Repositories where the work is happening

Bylaws

When a bug is resolved, the person who was assigned to it receives a bonus. Here is how it's calculated: First, assume that hours is how many hours it took to resolve the bug. Then, assume that self is 1 if the bug was reported and resolved by the same person, otherwise zero. Then, set days to hours ÷ 24, and award 12 points. Then, add 6 points if it was resolved in less than 16 hours. Then, deduct 8 points if they resolved the bug earlier reported by themselves. Then, deduct 0.5 points for each day of delay, but no more than -20 points. Then, make sure the reward is not larger than 16 points and not smaller than 4 points.

When someone pushes directly to the default branch, they get a penalty. Here is how it's calculated: Just -8 points.

An author of every code review receives a bonus. Here is how it's calculated: First, assume that hoc is the total number of hits-of-code in the contribution. Then, assume that comments is the total number of comments made by all reviewers. Then, assume that self is 1 if the review was made for their own code contribution, otherwise zero, and award 18 points. Then, deduct 12 points if they reviewed their own contribution. Then, add 0.015 points for each hit-of-code, but not more than 16 points. Then, deduct 5 points if there were less than 9 comments made during review. Then, deduct 8 points if there were absolutely no comments made during review. Then, add 0.375 points for each comment during the review, but not more than 8 points. Then, deduct 4 points if there were less than 24 hits-of-code. Then, make sure the reward is not larger than 24 points and not smaller than 4 points.

When a code contribution is made, the author receives a bonus. Here is how it's calculated: First, assume that hoc is the total number of hits-of-code in the contribution. Then, assume that comments is the total number of comments made by all reviewers. Then, assume that reviews is the number of reviews provided, and award 24 points. Then, add 0.075 points for each hit-of-code, but not more than 16 points. Then, deduct 4 points if more than 133 hits-of-code. Then, deduct 8 points if more than 533 hits-of-code. Then, deduct 8 points if there were no code review. Then, deduct 0.1 points for every comment above 5 made during review, but not more than -16 points. Then, deduct 4 points if you contribute less than 30 hits-of-code. Then, make sure the reward is not larger than 24 points and not smaller than 4 points.

When a bug is reported and accepted by the team, the reporter receives a bonus. Here is how it's calculated: Just award 18 points.

If a branch has a name that doesn\'t obey the convention, a penalty is given to the author. Here is how it's calculated: Just deduct -6 points.

When a new release is published, everyone who contributed receives a bonus. Here is how it's calculated: First, assume that hoc is how many hits-of-code are in the release. Then, assume that contributors is how many people contributed to the release, and award 36 points. Then, add 0.015 points for each hit-of-code, but not more than 24 points. Then, make sure the reward is not larger than 32 points and not smaller than 4 points.

When an enhancement is suggested and accepted by the team, the reporter receives a bonus. Here is how it's calculated: Just award 18 points.

When an issue is submitted but then rejected by the team, the reporter receives a penalty. Here is how it's calculated: Just deduct -8 points.

Oversized pull requests get penalized. Here is how it's calculated: Just deduct -4 points.

Quality of Service (QoS)

Quantity of Deliverables (QoD)

Earned Value Analysis (EVA)

AC: 93401, EV: 88348, PV: 20923, CPI: +0.95, SPI: +4.22.

Dimensions of Terrain (DoT)

Dimensionw38w39w40w41w42w43w44w45
total_active_contributors131310109121111
total_commits1752917802173821746017668177471799018016
total_contributors6062596060636363
total_files24382502238223952423242424242424
total_forks191190181182185207210210
total_issues31613345350037734125441048234860
total_pulls62826475646065817142750577567786
total_releases879879837837837837837837
total_repositories1818171717171717
total_stars142142118119119119120120