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

Developer	Avatar	Branches	PRs	Commits	Files	Changes
Siddharth Dushantha		1	2/2/0	3	5	5714
Paul Pfeister		2	2/1/0	3	7	39
Michael		1	2/1/0	1	1	25
Maikel		1	0/1/0	1	2	13
Tobias		1	1/1/0	1	1	13
MR-VL		1	2/1/1	1	1	6
synth (Ixve)		0	0/0/1	0	0	0
None (L0mbart)		0	1/0/0	0	0	0
None (Soxtixe)		0	1/0/1	0	0	0
None (AAAEMPIRE)		0	1/0/0	0	0	0
Pasan Laksitha (Pasanlaksitha)		0	1/0/1	0	0	0
Peter Dave Hello (PeterDaveHello)		0	1/0/0	0	0	0

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

Report On: Fetch issues

Recent Activity Analysis

Recent GitHub issue activity for the Sherlock project shows a steady influx of new issues, with a mix of bug reports, feature requests, and user questions. Notably, there are several false positive reports (#2273, #2261) and site support requests (#2268, #2248). Some issues highlight installation challenges, particularly with dependencies like pandas and numpy on certain platforms (#1945). There is also a recurring theme of users struggling with installation and usage, as seen in multiple closed issues.

Anomalies and Themes

• False Positives: Several issues report false positives for specific sites, such as Fiverr (#2162) and Genius.com (#1966), indicating potential changes in site structures or detection logic that need addressing.
• Installation Challenges: Many users face difficulties installing Sherlock, especially on non-standard environments like Termux or when using outdated guides (#1701, #1698).
• Feature Requests: Requests for new features or site support are common, with users suggesting enhancements like game-related categorization (#2084) and support for new sites like Threads.net (#2234).
• Documentation Gaps: Several issues stem from unclear documentation or outdated installation instructions, leading to user confusion (#1794).

Issue Details

Most Recently Created Issues

• #2275: Stubs required for statically typed downstreams (Enhancement)

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

• #2273: False positive for: A List of Websites (False Positive)

  • Created: 1 day ago
  • Status: Open
  • Priority: High

Most Recently Updated Issues

• #2255: Unable to use Sherlock (Bug)

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

• #2258: Sherlock is not working (Bug)

  • Created: 12 days ago
  • Updated: 4 days ago
  • Status: Open
  • Priority: High

The project continues to evolve with active community engagement, addressing both technical challenges and user experience improvements.

Report On: Fetch pull requests

Overview

The Sherlock Project is an open-source Python tool designed to search for social media accounts across multiple platforms using a given username. The project is actively maintained with numerous open pull requests (PRs) and a significant number of closed PRs, indicating ongoing development and community engagement.

Summary of Pull Requests

1. #2274: Adds Kaskus site to the Sherlock database, updating data.json with new site information.
2. #2272: Removes unnecessary apt-get update in Dockerfile to optimize Docker image build time.
3. #2271: Introduces devcontainer.json for development container configuration.
4. #2269: Reintroduces Fanpop site, previously removed, with several fixes.
5. #2267: Deprecates Python 3.8 support due to upcoming end-of-life and compatibility issues with dependencies.
6. #2200: Removes Tor support, suggesting users use the --proxy option instead.
7. #2170: Introduces --tag optional argument for sites requiring additional tag information alongside usernames.
8. #2169: Adds --tag flag functionality for searching usernames with tags, enhancing search capabilities.
9. #2143: Refactors the script entry point for better command-line argument parsing and integration into other Python scripts.
10. #2094: Adds a React frontend and API for web-based access to Sherlock, expanding its usability beyond the command line.

Analysis of Pull Requests

The Sherlock Project's pull requests reveal several key themes and ongoing efforts:

1. Feature Expansion: Many PRs focus on expanding the tool's capabilities by adding support for new sites (#2274, #2269), introducing new functionalities like tag handling (#2170, #2169), and enhancing user interface options such as a React frontend (#2094). This indicates a strong emphasis on making Sherlock more versatile and user-friendly.

2. Optimization and Maintenance: Several PRs aim to optimize existing features or maintain compatibility with evolving technologies. For example, removing unnecessary commands from the Dockerfile (#2272) improves build efficiency, while deprecating Python 3.8 (#2267) ensures future compatibility with key libraries like pandas and numpy.

3. Development Environment Improvements: The addition of devcontainer.json (#2271) highlights efforts to streamline the development process, making it easier for contributors to set up consistent environments.

4. Backward Compatibility and Transition Management: The removal of Tor support (#2200) and the introduction of optional arguments like --tag (#2170) reflect careful consideration of backward compatibility and user transition strategies. These changes are communicated clearly to users, ensuring a smooth transition without disrupting existing workflows.

5. Community Engagement and Contribution: The project shows active community involvement, with numerous contributors proposing enhancements and fixes. This is evident in the diverse range of PRs addressing various aspects of the project, from code refactoring (#2143) to documentation updates (#1908).

Overall, the Sherlock Project demonstrates a robust development process characterized by continuous feature enhancement, optimization efforts, and strong community collaboration. However, some older PRs remain open for extended periods (e.g., #1576), indicating potential areas where prioritization or resource allocation could be improved to address longstanding issues or feature requests more efficiently.

Report On: Fetch commits

Repo Commits Analysis

Development Team and Recent Activity

Team Members and Activities

• Paul Pfeister (ppfeister)

  • Recent activities include merging pull requests, fixing file not found issues, and deprecating Python 3.8 support.
  • Collaborated with Siddharth Dushantha on multiple occasions.
  • Worked on branches: master, 2266-deprecate-support-for-python-38.

• Siddharth Dushantha (sdushantha)

  • Involved in removing ICQ.com, updating the Sherlock path, adding Threads feature, and fixing merge conflicts.
  • Active in merging pull requests and resolving issues.
  • Worked on branch: master.

• MR-VL

  • Removed ICQ.com from the dataset.
  • Worked on branch: master.

• Michael (ntexe)

  • Implemented a feature to disable the creation of a txt file.
  • Worked on branch: master.

• Tobias (Txbias)

  • Removed Codeforces from documentation.
  • Worked on branch: master.

• Maikel (Netail)

  • Fixed merge conflicts and added Threads feature.
  • Worked on branch: master.

Patterns, Themes, and Conclusions

• The team is actively maintaining the project with frequent updates and bug fixes.
• There is a focus on removing outdated or unsupported features such as ICQ.com and Codeforces.
• Collaboration among team members is evident, particularly between Paul Pfeister and Siddharth Dushantha.
• The project is undergoing continuous improvements with new features like disabling txt file creation and adding Threads support.
• Deprecation of older Python versions indicates an effort to keep the project updated with current dependencies.

Overall, the development team is engaged in active maintenance, feature enhancements, and collaborative efforts to improve the Sherlock Project.