"LeetCode-Questions-CompanyWise" is a GitHub repository created by krishnadey30 that collects and organizes LeetCode coding questions by company, sorted by frequency and relevance. It aims to help developers prepare for technical interviews.
Despite its popularity (7,479 stars and 2,947 forks), the project has seen a significant slowdown in development activity. The last commit was made 516 days ago, and there have been no merged pull requests in over 432 days. However, user interest remains high, with recent issues and pull requests indicating a desire for updated content and improved organization.
The most recent pull requests and issues focus on content updates and structural improvements:
These activities suggest users are still engaged with the project and seeking improvements, despite the lack of recent updates from the maintainers.
The development team's recent activities have been minimal:
Krishna Kumar Dey (krishnadey30)
Ayush (shanurwt)
Sajal072004
The repository has only 9 total commits since its creation in August 2020, indicating infrequent but potentially substantial updates.
There's a recurring request (Issue #7) for the script used to generate the question lists, suggesting users want to contribute to or replicate the data collection process.
Basic structural improvements, such as adding header rows to CSVs (Issue #9), have been requested but remain unaddressed after 939 days.
The project's popularity (7,479 stars) contrasts sharply with its low commit count and recent inactivity, suggesting a disconnect between user interest and active maintenance.
The absence of a README file (Issue #57) is notable for a project of this size and popularity, indicating a need for improved documentation and user guidance.
| Timespan | Opened | Closed | Comments | Labeled | Milestones |
|---|---|---|---|---|---|
| 7 Days | 0 | 0 | 0 | 0 | 0 |
| 30 Days | 0 | 0 | 0 | 0 | 0 |
| 90 Days | 1 | 0 | 0 | 1 | 1 |
| 1 Year | 3 | 0 | 3 | 3 | 1 |
| All Time | 9 | 1 | - | - | - |
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.
Recent GitHub issue activity for this project has been moderate, with the most recent issue created 89 days ago. The issues primarily revolve around requests for updates, clarifications, and improvements to the repository's content and structure.
Several issues stand out as particularly significant:
Issue #60 requests the addition of the latest questions from 2024 LeetCode premium, indicating a need for up-to-date content.
Issue #57 highlights confusion about the meaning of time-based categories (1 year, 2 year, 6 months) and requests a README file for clarification. This issue reveals a lack of clear documentation, which could be hindering user understanding and usage of the repository.
Issue #7 and its comments demonstrate sustained interest in obtaining the script used to generate the question lists. This recurring request suggests that users are keen on contributing to or replicating the data collection process, but the absence of this script is a limitation.
Issue #9 proposes adding header rows to the CSVs, which would improve data readability and usability. The fact that this basic structural improvement remains unaddressed after 939 days is concerning.
Issues #1 and #10 both relate to the structure and content of the CSV files, indicating that data organization and accessibility could be improved.
A common theme among these issues is the desire for more recent data and improved organization of the existing information. The repository maintainers seem somewhat responsive, but many issues remain open for extended periods, suggesting that updates and improvements may be infrequent.
Most recently created issue:
Most recently updated issues: 1. #57: "Add a readme" (Open, created 279 days ago, updated 166 days ago) 2. #9: "Add Headings row to CSVs" (Open, created 939 days ago, updated 516 days ago) 3. #7: "Script to get this list?" (Open, created 1029 days ago, updated 635 days ago)
Other notable issues:
The dataset provides information on 53 pull requests (3 open, 50 closed) for the "LeetCode-Questions-CompanyWise" repository by krishnadey30, a popular resource for coding interview preparation.
The pull request history of the "LeetCode-Questions-CompanyWise" repository reveals several interesting patterns and points of analysis:
Recent Activity: The repository has seen some recent activity with three open pull requests (#62, #61, #59) in the last 103 days. However, the frequency of merged PRs has significantly decreased compared to earlier periods, potentially indicating a slowdown in active development or maintenance.
Bulk Updates: A significant number of pull requests (#54 to #19) were created and closed around 516-517 days ago, all related to adding headers to various files. This suggests a major restructuring or standardization effort in the repository at that time.
Content Additions: Several PRs focus on adding new content, such as company-specific questions (#12), interview questions (#61), and important resources (#56). This aligns with the repository's purpose of being a comprehensive resource for coding interview preparation.
Maintenance and Corrections: PRs like #62 (correcting typos) and #6 (beautifying CSV files) indicate ongoing efforts to improve the quality and presentation of the existing content.
Company-Specific Updates: Updates to questions for specific companies (e.g., Spotify in #5 and #4, Google in #3) show that the repository is being updated to reflect current interview trends for different companies.
Lack of Recent Merges: Despite having three open PRs, there hasn't been a merged PR in over 432 days (since #56). This could indicate a lack of active maintainers or a more stringent review process.
Community Contributions: The presence of multiple contributors submitting PRs suggests community involvement in improving and expanding the repository's content.
Potential Stagnation: The decreasing frequency of merged PRs and the presence of long-standing open PRs (up to 103 days old) might indicate some level of project stagnation or reduced maintenance.
Structural Changes: PRs like #59 creating a README file suggest that even basic repository structure elements were added later in the project's lifecycle, indicating organic growth and evolution of the project.
In conclusion, while the repository has seen significant development and community interest in the past, the recent slowdown in merged PRs and the presence of long-standing open PRs suggest that the project may benefit from more active maintenance. The continued submission of PRs indicates ongoing interest from the community, but the project maintainers may need to re-engage to keep the resource current and valuable for its users.
Krishna Kumar Dey (krishnadey30)
Ayush (shanurwt)
snordale
Saurav Das (SauravDas90)
sidsm009
Sajal072004
Low recent activity: The most recent commit was 516 days ago, indicating a lack of recent updates to the repository.
Focus on data organization: Recent commits primarily involved adding headers and organizing CSV files.
Community contributions: Multiple contributors have made small updates to improve the repository's structure and content.
Infrequent updates: With only 9 total commits since creation, updates appear to be infrequent but potentially significant.
Ongoing engagement: Despite the lack of recent commits, there is still some community involvement, as evidenced by Sajal072004's recent pull request.
Maintenance of existing content: Recent activities focused on improving existing data rather than adding new content.
Summary
Quantified Reports
Detailed Reports