Quantify Issues

Recent GitHub Issues Activity

_{Like all software activity quantification, these numbers are imperfect but sometimes useful. Comments, Labels, and Milestones refer to those issues opened in the timespan in question.}

Quantify commits

Quantified Commit Activity Over 30 Days

_{PRs: created by that dev and opened/merged/closed-unmerged during the period}

Report On: Fetch issues

Recent Activity Analysis

The Sherlock project has seen a recent surge in activity, with 97 open issues currently being tracked. Notably, several issues have been raised concerning false positives, particularly with sites like Reddit and Fiverr, indicating potential reliability concerns in the tool's functionality. Additionally, there are multiple requests for support for new sites, reflecting ongoing interest in expanding the tool's capabilities. The presence of numerous bug reports related to installation and operational errors suggests that users may be facing challenges with the latest updates or installation methods.

Notable Issues

1. False Positives: Issues #2299 (Reddit) and #1788 (Fiverr) highlight ongoing concerns where the tool incorrectly identifies usernames as existing on these platforms.
2. Installation Errors: Multiple users have reported difficulties installing dependencies, particularly on Termux (#1945) and other environments (#1820).
3. Site Support Requests: There are active requests for adding support for various platforms, including Codeforces (#1654) and CSSBattle (#1804), which indicates a growing demand for broader coverage.

Issue Details

Most Recently Created Issues

1. Issue #2314: Requesting support for Atcoder

   • Priority: Low
   • Status: Open
   • Created: 3 days ago
   • Updated: 2 days ago

2. Issue #2313: Long Fake Username has Many False Positives

   • Priority: High
   • Status: Open
   • Created: 4 days ago
   • Updated: 1 day ago

3. Issue #2311: Requesting support for VLR.gg

   • Priority: Low
   • Status: Open
   • Created: 6 days ago

4. Issue #2308: 403 and 404 Errors Still Persist When Querying Usernames

   • Priority: Medium
   • Status: Open
   • Created: 8 days ago

5. Issue #2306: Requesting support for Topcoder

   • Priority: Low
   • Status: Open
   • Created: 9 days ago

Most Recently Updated Issues

1. Issue #2314: Requesting support for Atcoder

   • Updated by Milan Variya with a pull request link to address the issue.

2. Issue #2313: Long Fake Username has Many False Positives

   • Multiple users have commented on their experiences with this bug, indicating it is a common issue.

3. Issue #2308: 403 and 404 Errors Still Persist When Querying Usernames

   • Ongoing discussions about potential causes of these errors, including IP flagging.

4. Issue #2298: run sherlock user123 get error bad response while accessing data file URL

   • Discussion about incorrect URLs leading to errors when accessing necessary data files.

5. Issue #2295: PIP installing error

   • Users discussing installation issues related to package management.

Summary

The analysis of current GitHub issues reveals significant user engagement with both feature requests and bug reports, particularly around false positives and installation challenges. The community appears active in seeking solutions and contributing to the project's growth through requests for new site integrations and addressing existing bugs.

Report On: Fetch pull requests

Overview

The analysis of the pull requests (PRs) for the Sherlock project reveals a dynamic and active development environment. The PRs cover a wide range of enhancements, bug fixes, and new feature additions, reflecting the project's commitment to continuous improvement and responsiveness to community contributions.

Summary of Pull Requests

Open Pull Requests

• PR #2316: Add support for Atcoder

  • Adds support for Atcoder, a competitive programming platform.

• PR #2312: Adding DigitalSpy

  • Integrates support for Digital Spy, a UK-based entertainment and media news website.

• PR #2310: add VLR.gg support

  • Implements support for VLR.gg, a platform related to esports.

• PR #2309: add support for Topcoder

  • Adds functionality to check usernames on Topcoder, a competitive programming platform.

• PR #2307: Update site-list.py

  • Improves readability and maintains functionality in site-list.py.

• PR #2304: Updated Project Description & Added Common Installation Issues

  • Updates project description in README and adds common installation issues.

• PR #2303: add Bluesky support (#2302)

  • Adds support for Bluesky, addressing potential issues with user existence checks.

• PR #2291: fixed speedrun site support #2288

  • Fixes duplication and error checking issues with the speedrun site support.

• PR #2283: Adding support for exophase via data.json for #2248

  • Implements support for Exophase, a gaming profile aggregator.

Closed Pull Requests

• PR #2315: Add support for Atcoder

  • Initially added Atcoder support but was closed after merging changes under a different commit due to GitHub's handling of squashed commits.

• PR #2276: Add site Gitea.com

  • Successfully merged, adding Gitea.com to the list of supported sites.

• PR #2274: add kaskus site

  • Merged to include Kaskus, an Indonesian online community forum.

• PR #2272: Remove not needed apt-get update in Dockerfile

  • Merged to optimize Dockerfile by removing unnecessary apt-get update.

Analysis of Pull Requests

The PRs indicate a robust contribution pattern with a focus on expanding the tool's capabilities across various platforms. The addition of sites like Atcoder, Digital Spy, and VLR.gg showcases the project's adaptability to include emerging or niche platforms. The contributions also reflect an active effort to maintain and improve existing functionalities, as seen in PRs addressing bug fixes and enhancements like those for speedrun site support and Exophase integration.

The closed PRs reveal effective collaboration within the community, with quick responses to contributions that enhance the project's scope. The handling of PR #2315 illustrates an efficient workflow where contributions are integrated even if initial PRs are closed due to procedural reasons like squashing commits.

Overall, the Sherlock project's pull request activity highlights its vibrant community and ongoing commitment to enhancing its toolset for users interested in managing their online identities across a growing number of social networks.

Report On: Fetch commits

Repo Commits Analysis

Development Team and Recent Activity

Team Members

1. Paul Pfeister (ppfeister)

   • Recent Activities:
   • Merged multiple pull requests related to Dockerfile optimizations and site updates.
   • Worked on deprecating Python 3.8 due to EOL concerns.
   • Contributed to PEP compliance and updated documentation for Fedora and Parrot.
   • Active in fixing bugs and enhancing CI workflows.

2. Siddharth Dushantha (sdushantha)

   • Recent Activities:
   • Fixed various false positives in the tool's detection capabilities.
   • Contributed to the removal of outdated sites and cleanup of project directories.
   • Collaborated with Paul on several pull requests, including testing actions and documentation updates.

3. Michael (ntexe)

   • Recent Activities:
   • Restored functionality for Fanpop and added new features such as disabling txt file creation.
   • Engaged in collaborative efforts with other team members on feature enhancements.

4. Maikel (Netail)

   • Recent Activities:
   • Worked on adding features like Threads and fixing merge conflicts.
   • Involved in minor bug fixes and enhancements.

5. Tobias (Txbias)

   • Recent Activities:
   • Contributed to the removal of Codeforces from the project.
   • Engaged in updating documentation related to site formats.

Summary of Recent Commits

• The team has been actively merging pull requests, focusing on bug fixes, feature additions, and documentation improvements.
• Significant collaboration is evident among team members, particularly between Paul Pfeister and Siddharth Dushantha, who frequently co-author commits and address issues together.
• The recent activity indicates a commitment to maintaining the tool's functionality across various platforms while also ensuring compliance with evolving standards (e.g., PEP 561).
• There are ongoing efforts to clean up the codebase, remove deprecated features, and enhance user documentation.

Patterns and Themes

• Collaboration: Strong teamwork is evident, particularly in merging pull requests and addressing issues collectively.
• Maintenance Focus: A significant portion of recent activity is dedicated to maintaining compatibility with dependencies and improving overall code quality.
• Feature Development: Continuous enhancement of features suggests a proactive approach to user needs, particularly in adapting to changes in social media platforms.
• Documentation Improvements: Regular updates to documentation indicate an emphasis on usability and support for users.

Conclusions

The development team is actively engaged in maintaining and enhancing the Sherlock project, demonstrating effective collaboration and a focus on both user experience and technical compliance. The recent activities reflect a balanced approach between feature development, bug fixing, and documentation efforts.