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
James George		2	6/6/0	8	59	3000
Mir Arif Hasan		5	3/3/0	30	28	2732
Andrew Bastin		1	2/2/0	5	26	1835
Tasnim Tantawi		1	1/1/0	1	1	1248
Joel Jacob Stephen		1	1/3/0	3	25	948
Akash K		1	4/4/0	4	18	607
Nivedin		3	4/3/0	5	15	386
Balu Babu		5	1/3/0	9	12	204
Anwarul Islam		1	1/1/0	1	2	81
Paul Vogel		1	2/2/0	2	1	40
Dmitry		1	1/1/0	1	2	7
artu-ole		1	1/1/0	1	2	4
Muhammed Ajmal M		1	1/1/0	1	1	2
Christian Hansen (ch99q)		0	1/0/0	0	0	0
Abhijith Kp (ikp-773)		0	1/0/0	0	0	0
None (HelixY2J)		0	2/0/1	0	0	0
Govind.S.B (Govind-S-B)		0	0/0/1	0	0	0
Jean-Paul van Ravensberg (DevSecNinja)		0	1/0/0	0	0	0
Palak Chopra (ipalakchopra)		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

The Hoppscotch project has recently experienced a surge in activity, with 372 open issues currently documented on GitHub. Notably, several issues have emerged around the functionality of the application, particularly concerning OAuth2 authentication, environment variable management, and UI bugs related to request handling. A recurring theme is the struggle with user authentication methods, especially in self-hosted environments, where users report difficulties with email and OAuth logins. Additionally, there are multiple reports of bugs affecting the desktop application across various operating systems.

Issue Details

Most Recently Created Issues

1. Issue #4291: [bug]: Installation error under OpenShift

   • Priority: High
   • Status: Open
   • Created: 0 days ago
   • Update: N/A

2. Issue #4289: [bug]: Admin Dashboard and Login pane not showing up, 405 and configuration errors

   • Priority: High
   • Status: Open
   • Created: 0 days ago
   • Update: N/A

3. Issue #4286: [bug]: The inherit header is not showing in code snippet

   • Priority: Medium
   • Status: Open
   • Created: 1 day ago
   • Update: N/A

4. Issue #4285: Save Button Fails to Save Newly Generated Token in Teams Workplace

   • Priority: Medium
   • Status: Open
   • Created: 1 day ago
   • Update: N/A

5. Issue #4283: [bug]: "Could not send request" when sending cookies with a newline or %0 character.

   • Priority: Medium
   • Status: Open
   • Created: 2 days ago
   • Update: N/A

Most Recently Updated Issues

1. Issue #4244: [bug]: 2024.7.1 backend docker image start failed with error "listen tcp :80: bind: permission denied"

   • Priority: High
   • Status: Open
   • Last Updated: 4 days ago

2. Issue #4258: [bug]: Code Challenge missing when using OAuth with PKCE

   • Priority: Medium
   • Status: Open
   • Last Updated: 10 days ago

3. Issue #4259: [bug]: Written Error

   • Priority: Medium
   • Status: Open
   • Last Updated: 10 days ago

4. Issue #4260: [bug]: Tt.auth.getAllowedAuthProviders is not a function.

   • Priority: High
   • Status: Open
   • Last Updated: 10 days ago

5. Issue #4261: [bug]: Cookies not sent with GET

   • Priority: Medium
   • Status: Open
   • Last Updated: 10 days ago

Analysis of Notable Issues

Several issues exhibit common patterns that may indicate systemic problems within the application:

• Many users are experiencing difficulties with OAuth2 authentication flows, particularly when using client credentials or magic links for login (e.g., issues #4291, #4289). This suggests potential flaws in how authentication tokens are managed or generated.

• The presence of multiple issues related to UI elements (e.g., disappearing buttons, misaligned panels) indicates that recent updates may have introduced regressions affecting user experience (e.g., issues #4286, #4285).

• A significant number of issues involve environment variable management and persistence (e.g., issue #4254), hinting at a need for improved handling of user settings and configurations across sessions.

• The problems reported regarding the desktop application crashing or failing to open (e.g., issues #4291, #4258) suggest that there may be broader compatibility or stability concerns that need addressing.

Overall, these issues highlight critical areas for improvement in both functionality and user experience within Hoppscotch, particularly as it continues to evolve as an open-source API development tool.

Report On: Fetch pull requests

Report on Pull Requests

Overview

The analysis covers a total of 38 open pull requests (PRs) from the Hoppscotch repository, highlighting recent contributions to feature enhancements, bug fixes, and localization improvements. The PRs reflect ongoing development efforts aimed at improving the user experience, expanding functionality, and maintaining code quality.

Summary of Pull Requests

1. PR #4290: feat: Updated and corrected Danish translations

   • State: Open
   • Created: 0 days ago
   • Significance: This PR enhances the localization of the Hoppscotch interface by correcting Danish translations, ensuring better user experience for Danish-speaking users.

2. PR #4282: HSB-482 fix: add env missing checks

   • State: Open
   • Created: 2 days ago
   • Significance: Introduces checks for missing environment variables in the .env file, improving error handling and robustness.

3. PR #4280: feat: sort environments alphabetically

   • State: Open
   • Created: 3 days ago
   • Significance: Enhances usability by sorting environment entries alphabetically in the sidebar and selector.

4. PR #4275: feat(cli): add support for request variables

   • State: Open
   • Created: 4 days ago
   • Significance: Adds functionality for request variables in the CLI, allowing for more dynamic API testing.

5. PR #4269: Add Open Containers Initiative (OCI) labels

   • State: Open
   • Created: 7 days ago
   • Significance: Implements OCI labels to improve Docker image management and compatibility with tools like Renovate Bot.

6. PR #4187: feat: description field for request parameters and headers

   • State: Open
   • Created: 40 days ago
   • Significance: Introduces a description field for API documentation, enhancing clarity and usability.

7. PR #4142: feat: new request auth types

   • State: Open
   • Created: 60 days ago
   • Significance: Expands authentication options available in Hoppscotch, increasing flexibility for developers.

8. PR #4218: [feature]: workflows for API testing

   • State: Open
   • Created: 26 days ago
   • Significance: Introduces a node-based system for designing API test workflows, enhancing testing capabilities.

9. PR #4216: refactor: make global environment a versioned entity

   • State: Open
   • Created: 26 days ago
   • Significance: Updates global environment schema to be versioned, improving data integrity and management.

10. PR #4215: Adding loading state for Hopss import modal collection

    • State: Closed (Not merged)
    • Created: 26 days ago
    • Significance: Aims to improve user feedback during collection imports but was not accepted.

Analysis of Pull Requests

The recent activity within the Hoppscotch repository reveals several key themes:

Localization Efforts

A strong emphasis on localization is evident from multiple PRs aimed at improving translations (e.g., PRs #4290 and #4196). This indicates a commitment to making Hoppscotch accessible to non-English speaking users, which is crucial for broadening its user base.

Feature Enhancements

Numerous PRs focus on adding new features or enhancing existing ones (e.g., PRs #4280, #4275). The addition of features such as sorting environments alphabetically and supporting request variables reflects an ongoing effort to improve usability and functionality. These enhancements are likely to increase user satisfaction and engagement with the tool.

Bug Fixes and Improvements

Several PRs address bugs or improve existing functionalities (e.g., PRs #4282 and #4181). The proactive approach to fixing issues related to environment variable checks and UI inconsistencies demonstrates a commitment to maintaining high-quality software standards.

Collaboration and Community Engagement

The presence of multiple contributors working on various aspects of the project indicates a healthy collaborative environment. The discussions around PRs, especially those that were not merged (e.g., PR #4215), show an active community that values feedback and seeks consensus on changes.

Anomalies

While there is significant activity in open PRs, some older PRs remain unmerged or have stalled (e.g., PRs from over two months ago). This could indicate potential bottlenecks in the review process or shifts in project priorities that may need addressing to maintain momentum in development.

Conclusion

Overall, the current state of pull requests in the Hoppscotch repository reflects a vibrant development ecosystem focused on continuous improvement through feature enhancements, bug fixes, and localization efforts. However, attention should be given to older PRs that may require review or closure to streamline project management processes.

Report On: Fetch commits

Repo Commits Analysis

Development Team and Recent Activity

Team Members and Activities

1. Nivedin (nivedin)

   • Recent Commits: 5 commits, 386 changes.
   • Notable Contributions:
   • Fixed request execution context persistence between tabs.
   • Collaborated on UI updates for WhatsNewDialog.
   • Worked on resetting environment variables during shared workspace changes.
   • Ongoing Work: Sorting environments alphabetically in the sidebar.

2. Andrew Bastin (AndrewBastin)

   • Recent Commits: 5 commits, 1835 changes.
   • Notable Contributions:
   • Bumped version to 2024.7.2.
   • Fixed port binding issues across different container runtimes.
   • Contributed to multiple package.json updates.
   • Ongoing Work: None reported.

3. James George (jamesgeorge007)

   • Recent Commits: 8 commits, 3000 changes.
   • Notable Contributions:
   • Fixed issues with the Content-Type header in CLI requests.
   • Worked on syncing settings actions in self-hosted environments.
   • Collaborated on various bug fixes and feature enhancements.
   • Ongoing Work: None reported.

4. Anwarul Islam (anwarulislam)

   • Recent Commits: 1 commit, 81 changes.
   • Notable Contributions:
   • Updated WhatsNewDialog UI and position.
   • Ongoing Work: None reported.

5. Dmitry Mukovkin (shipko)

   • Recent Commits: 1 commit, 7 changes.
   • Notable Contributions:
   • Improved body tab functionality and fixed RawBody empty string bug.
   • Ongoing Work: None reported.

6. Tasnim Tantawi (tasnim0tantawi)

   • Recent Commits: 1 commit, 1248 changes.
   • Notable Contributions:
   • Completed Arabic translations with extensive updates.
   • Ongoing Work: None reported.

7. Paul Vogel (pavog)

   • Recent Commits: 2 commits, 40 changes.
   • Notable Contributions:
   • Added and fixed German translations for various sections.
   • Ongoing Work: None reported.

8. Akash K (amk-dev)

   • Recent Commits: 4 commits, 607 changes.
   • Notable Contributions:
   • Added analytics events for AI experiments and enabled them by default in settings.
   • Ongoing Work: None reported.

9. Mir Arif Hasan (mirarifhasan)

   • Recent Commits: 30 commits, 2732 changes.
   • Notable Contributions:
   • Introduced infra tokens to the admin dashboard and added user management APIs.
   • Worked extensively on encryption features for sensitive data storage.
   • Ongoing Work: Multiple branches related to infra token features.

10. Joel Jacob Stephen (JoelJacobStephen)

    • Recent Commits: 3 commits, 948 changes.
    • Notable Contributions:
    • Improved invite flow in the admin dashboard and resolved rendering issues for images.
    • Ongoing Work: None reported.

Patterns and Themes

• Collaboration: Several commits were co-authored, indicating a collaborative development environment where team members frequently work together on features and fixes.
• Focus on Bug Fixes: A significant number of recent commits are dedicated to fixing bugs, particularly around UI elements and request handling, showcasing an emphasis on improving user experience and stability of the application.
• Internationalization Efforts: There is ongoing work related to translations into Arabic and German, reflecting a commitment to making the tool accessible to a broader audience.
• Feature Enhancements: The team is actively working on enhancing existing features such as environment management and user settings synchronization, indicating a focus on improving core functionalities of the Hoppscotch platform.

Conclusions

The development team is actively engaged in maintaining and enhancing the Hoppscotch project with a balanced focus on bug fixes, feature development, and internationalization efforts. The collaborative nature of their work suggests a strong team dynamic that fosters innovation while addressing user needs effectively.