@SwaroopHCurrent employee
- PRs merged
- 57
- Internal authors supported
- 6
- Currently active authors
- 1
- First merge
- Jan 18, 2023
- Last merge
- Jul 21, 2026
Active leadEarly maintainer
Internal authors whose PRs they merged
Back to Organizations
Powerloom
Powerloom is a decentralized data protocol for Web3 that provides consensus-backed, peer-validated onchain data through a network of snapshotter nodes, validators, and configurable data markets, serving developers, DeFi dashboards, bots, and AI agents. As of mid-2026 the founders announced an orderly wind-down of the project, with the chain and hosted services being shut down.
Distributed
Current stage: Seed2 current maintainers2 active leads2 new active leads1 lead step-down1 early lead departure
Maintainer signals as of Aug 10, 2026
Maintainer Intelligence
This view starts from the canonical internal-employee model. A maintainer is an internal employee who merged at least one pull request in a non-fork repository; external contributors, bots, and PR authors are not treated as causal. Active leads have merged within the last three months.
2
Current maintainers
2
Active leads
2
New active leads
1
Lead step-downs
0
Lead movements
1
Early lead departures
Signals as of Aug 10, 2026github.com/powerloom
Maintainers (11)
Open GitHub profile ↗
@anomitCurrent employee
- PRs merged
- 95
- Internal authors supported
- 9
- Currently active authors
- 1
- First merge
- Nov 23, 2020
- Last merge
- Jun 14, 2026
Active leadEarly maintainer
Internal authors whose PRs they merged
@xadahiyaFormer employee
- PRs merged
- 73
- Internal authors supported
- 7
- Currently active authors
- 2
- First merge
- Jan 16, 2023
- Last merge
- Oct 6, 2025
Early maintainer
Internal authors whose PRs they merged
@Seth-SchmidtFormer employee
- PRs merged
- 0
- Internal authors supported
- 0
- Currently active authors
- 0
- First merge
- Mar 28, 2024
- Last merge
- Aug 29, 2025
Early maintainer
Open GitHub profile ↗@chetna-mittalFormer employee
- PRs merged
- 0
- Internal authors supported
- 0
- Currently active authors
- 0
- First merge
- Dec 17, 2024
- Last merge
- Jan 6, 2025
@SulejmanFormer employee
- PRs merged
- 1
- Internal authors supported
- 1
- Currently active authors
- 0
- First merge
- Aug 1, 2024
- Last merge
- Sep 10, 2024
Early maintainer
Internal authors whose PRs they merged
@muku314115Former employee
- PRs merged
- 2
- Internal authors supported
- 1
- Currently active authors
- 0
- First merge
- May 30, 2024
- Last merge
- Aug 1, 2024
Early maintainer
Internal authors whose PRs they merged
@thecoderpandaFormer employee
- PRs merged
- 0
- Internal authors supported
- 0
- Currently active authors
- 0
- First merge
- Feb 21, 2024
- Last merge
- Feb 21, 2024
@getjiggyFormer employee
- PRs merged
- 3
- Internal authors supported
- 2
- Currently active authors
- 0
- First merge
- Dec 12, 2023
- Last merge
- Feb 19, 2024
Early maintainer
Internal authors whose PRs they merged
@swagftwFormer employee
- PRs merged
- 0
- Internal authors supported
- 0
- Currently active authors
- 0
- First merge
- May 24, 2023
- Last merge
- Jun 13, 2023
@chaitanyapremFormer employee
- PRs merged
- 1
- Internal authors supported
- 1
- Currently active authors
- 1
- First merge
- Jan 13, 2023
- Last merge
- Jan 25, 2023
Early maintainer
Internal authors whose PRs they merged
Maintainer Movements (3)
@muku314115 moved lead merge authority to NodeOps Network.
Confirmed Apr 30, 2026 · Observed · Early maintainer
Last source merge Aug 1, 2024 · First destination merge Apr 30, 2026
@Seth-Schmidt moved lead merge authority to Zama.
Confirmed Feb 26, 2026 · Observed · Early maintainer
Last source merge Aug 29, 2025 · First destination merge Feb 26, 2026
@chaitanyaprem moved lead merge authority to Status.
Confirmed Jun 14, 2024 · Observed · Early maintainer
Last source merge Jan 25, 2023 · First destination merge Jun 14, 2024