Team Contribution Report Generator for Contract Repos
Free to download on every platform. Comes pre-installed on BotFone, BotPad and BotFlip — with extra free apps included.
About this app
WHAT IT DOES
This tool generates detailed contribution reports for development teams working on smart contract repositories. By aggregating GitHub activity across multiple repositories, it provides a comprehensive view of each team member's contributions—including commits, pull requests opened, issues created, and code reviews performed. The report maps repositories to their associated on-chain contracts using source verification data, enabling teams to understand development activity linked to production deployments. Results include per-contributor activity summaries, repository-level breakdowns, and aggregate statistics showing total commits, PRs, issues, and reviews across the team. This is essential for project managers tracking team productivity, auditors assessing development activity patterns, and teams preparing transparency reports for their communities.
HOW TO USE
Connect your wallet (read-only, no transaction required) and select the target network. Enter a list of GitHub repositories (format: owner/repo, one per line) that contain your contract source code. Provide a GitHub personal access token to increase rate limits and access private repositories (optional). Set the lookback period in days to define the analysis window. Click "generate contribution report" and the tool will fetch activity data via the GitHub API for each repository, aggregating contributions by username. Results display as a ranked list of contributors with their activity metrics, repository affiliations, and summary statistics including total commits, PRs, issues, and reviews across all repositories.
TECHNICAL MECHANISM
The analyzer uses the GitHub REST API to retrieve contribution data for each specified repository. For each repo, it fetches commits (including author information), pull requests (both open and closed), issues, and review comments via multiple API endpoints. The tool processes these responses to build a contributor-centric data model, aggregating activity across repositories while preserving per-repo association. It implements request queuing with backoff to respect GitHub API rate limits, processing repositories sequentially with visible progress updates. The tool optionally includes source verification mapping by checking block explorer APIs to confirm which contract addresses are deployed from each repository, adding on-chain deployment context to the contribution data. Results are sorted by total activity score (commits + PRs + reviews) to highlight the most active contributors.
WHAT IT CANNOT SEE
This tool cannot analyze repositories that are private or not accessible via the GitHub API without appropriate authentication tokens. It is limited by GitHub API rate limits, which may restrict the number of repositories and contributors that can be analyzed in a single session, especially without a GitHub token. It cannot detect contributions made through forked repositories, offline work not reflected in GitHub data, or commits pushed directly without associated GitHub issues or PRs. It cannot correlate on-chain deployment activity with GitHub contributions unless source code mappings are available through block explorer verification data. The accuracy of results depends on the completeness and accuracy of GitHub metadata and block explorer verification data. It cannot distinguish between different team members with similar GitHub usernames or detect contributions made using organization-level accounts. It cannot analyze contribution quality or code impact beyond basic commit and PR metrics. The tool is limited to repositories that have at least one verified contract deployed on-chain when attempting contract mapping; otherwise, it operates purely on GitHub data.
PLEASE NOTE
This is a read‑only analytics tool—it never submits transactions or signs anything. It is designed for EVM‑compatible chains but can analyze GitHub data for any repository. For best results, provide a GitHub personal access token to increase API rate limits from 60 to 5,000 requests per hour. The tool respects GitHub's API terms of service and includes appropriate delays between requests to avoid rate limiting. Contribution data reflects GitHub activity only and does not capture other forms of team contribution such as design, documentation, or community management.