E

EmpCloud

conf 0.55

Thunder Marketing · 1Touch-dev

Team

23 people · 14 produced code · 8051h tracked

2026-06-28 → 2026-09-26 · showing up to 2026-09-26 · live data last updated 26 Sept, 08:33 UTC

People

23

with tracked time or code

Producing code

14

rankable cohort

Tracked time but no code

0

a question, not a verdict

No code account linked

5

no signal at all — never a low one

Not ranked on code

0

role is not code delivery

Roster

Sorted by signal. Click any name for the evidence behind their number.

#PersonSignalSeenComponentsHoursDaysAct%PRsMergedCommitsLinesStatus
1Abhishek Kulkarni
Abhishek9302
8594%
change discipline100
review15
craft99
consistency64
infrastructure97
completed work—
576.66523.2004902,953,753Steady

⚑ 1 flag

2Pankaj Kumar
pankaj1touch
8496%
craft93
change discipline97
review15
consistency73
infrastructure100
completed work—
666.1792100375694,930Steady

⚑ 1 flag

3Ankur Kumar
ankur1touch
7572%
change discipline100
review15
infrastructure51
craft99
consistency59
completed work—
768.48819.100191150,935Steady
4Anshuman Parmar
anshumankyma
7463%
craft97
change discipline100
infrastructure50
review15
consistency55
completed work—
561.27826.200189414,914Steady

⚑ 1 flag

5Aziz Bohra
AzizBohraKyma
7347%
infrastructure32
consistency45
change discipline100
craft99
review50
completed work—
583.26627.900250278,642Steady

⚑ 1 flag

6MOHD NAVED
MohdNaved123
7349%
change discipline89
consistency40
craft97
review15
completed work—
infrastructure—
344.14117.80053798,774Steady

⚑ 2 flags

7Pramod Soni
PRAMODS0NI
7340%
consistency23
craft97
change discipline100
review15
completed work—
infrastructure—
121.21530.5003017,283Steady
8Harsh Patel
harsh-kyma
7181%
craft58
change discipline100
review15
consistency59
infrastructure100
completed work—
526.06410.100195564,768Steady

⚑ 1 flag

9Manish Chandrakar
manishKyma
6774%
change discipline66
craft92
consistency53
review15
completed work—
infrastructure—
290.34319.900189579,790Steady

⚑ 1 flag

10Akash Kumar
AkashKyma
6653%
infrastructure18
consistency45
craft97
change discipline100
review15
completed work—
488.06016.6001001,064,329Steady

⚑ 2 flags

11Dhiraj Ambekar
Dhiraj4113
6473%
craft73
infrastructure46
consistency50
change discipline100
review15
completed work—
517.46421.9007779,767Steady
12Pranav Ojha
Pranav173261
6153%
craft51
consistency52
change discipline100
review15
completed work—
infrastructure—
457.36430.300235307,733Steady

⚑ 1 flag

13Jitu Prosad Saha
jitusaha11
5843%
infrastructure11
craft80
change discipline92
consistency45
review15
completed work—
521.76026.9007189,868Steady

⚑ 1 flag

14Rushikesh Powar
rushikesh-swe
5774%
infrastructure12
change discipline70
craft85
review15
consistency63
completed work—
552.06634.900156652,904Steady

⚑ 1 flag

·Rishav Raj
rishav1238
—25%too little data to rank in this period524.26942.9002059,785Unrankable

⚑ 1 flag

·Rushendra Varma Mudunuru
not linked
—85%identity unmapped246.5398.9————Unlinked

⚑ 1 flag

·mohammad saad
not linked
—0%identity unmapped173.52422————Unlinked

⚑ 1 flag

·Anmol Music
not linked
—0%identity unmapped115.41825.9————Unlinked

⚑ 1 flag

·Srija Bandapally
not linked
—0%identity unmapped16.1327.6————Unlinked

⚑ 1 flag

·Srija Bandapally
not linked
—0%identity unmapped1.4220.2————Unlinked

⚑ 1 flag

·Claude Code
claude
—100%no code in this period0.00—00144Outside cohort
·Cursor Agent
cursor-agent
—100%no code in this period0.00—006896Outside cohort
·Ruhani Allagh
not linked
——no code in this period0.00—————Outside cohort

Only people with a published score carry a rank. A dot means this period cannot place them — not that they placed last.

How to read this table

Three sentences that separate a fair dashboard from a harmful one.

  • A dash is not a zero. 5 people have no code account linked. They get no signal at all — printing 0 would assert they produced nothing.
  • “No code” is a question. 0 tracked time and landed nothing in these repos. The work may not be code, or may live where this platform cannot see.
  • Seen is the share of someone’s known working days that produced a commit, review, task or infrastructure change. It never changes a score — it says what the score is about. Below 35% the comparative band is withheld entirely: calling someone “behind” on a fifth of the evidence is a verdict this data cannot support.

    Hours and lines are never scored. They are shown for context.