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
Adrien Servel		8	17/14/1	42	229	55233
renovate[bot]		7	86/77/5	82	64	16787
Samuel Hassine		1	0/0/0	27	166	8293
Archidoit		4	11/11/0	18	111	7078
Laurent Bonnet		3	4/4/0	7	134	6018
Landry Trebon		8	9/7/1	38	103	4028
Fhwang		1	0/1/0	1	7	3636
Julien Richard		4	2/2/0	11	59	3460
Bonsai8863		2	2/0/0	6	148	3446
Céline Sèbe		8	8/5/1	32	94	2991
A. Jard		6	8/6/1	23	69	2065
Jean-Philippe Kha		1	0/0/0	1	3	1930
None (Gwendoline-FAVRE-FELIX)		1	1/0/0	6	15	1803
Francois GRUNERT		5	10/7/0	27	69	1771
Marie Flores		4	3/0/1	12	43	1520
Sarah Bocognano		5	6/4/0	13	39	1301
Frédéric BASLER		1	0/0/0	1	33	1245
ValentinBouzinFiligran		3	2/2/0	12	38	841
Jeremy Cloarec		4	5/4/0	23	22	798
abijahcalderon		2	0/0/0	2	20	732
Souad Hadjiat		4	6/4/0	9	17	460
Romy Alula		1	1/1/0	1	17	269
VerboseCat		1	1/0/0	1	16	224
Filigran Automation		3	0/0/0	9	4	72
dependabot[bot]		1	2/1/1	1	1	6
defendable-ole		1	1/1/0	1	1	2
Sébastien Bocahu		1	0/0/0	1	1	1
None (daimyo007)		0	4/0/2	0	0	0
Ikko Eltociear Ashimine (eltociear)		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 OpenCTI project has recently seen a surge in activity, with 1067 open issues currently logged. Notably, several critical bugs and feature requests have been raised, indicating ongoing development and user engagement. A significant number of issues are related to UI/UX improvements, performance enhancements, and integration capabilities, reflecting the community's focus on usability and functionality.

Several recurring themes emerge from the issues: 1. Bugs and Performance Issues: Many reports highlight performance degradation when handling large datasets or complex relationships, particularly in the context of background tasks and entity management. 2. Feature Requests: Users are actively requesting enhancements to the platform's capabilities, such as improved filtering options, better integration with external systems, and more intuitive UI elements. 3. Data Integrity Concerns: Issues surrounding the accuracy of data representation (e.g., duplicate entities or incorrect relationships) suggest a need for more robust validation mechanisms within the platform.

Issue Details

Recent Issues

1. Issue #8159: [Case Management]: Be able to quickly "update" some fields

   • Priority: Feature
   • Status: Open
   • Created: 2 days ago
   • Proposed Solution: Implement quick actions for updating processing status, priority, and severity.

2. Issue #8157: [background tasks] You can delete knowledge even if you don't have the capability

   • Priority: Critical
   • Status: Open
   • Created: 2 days ago
   • Description: Users can delete knowledge without appropriate permissions, leading to potential data loss.

3. Issue #8156: [Ext Ref Search] Some Ext Ref are not found in search

   • Priority: Bug
   • Status: Open
   • Created: 2 days ago
   • Description: Automatically created External References are not searchable after upload.

4. Issue #8155: Messages in push_sync queue unexpectedly truncated

   • Priority: Bug
   • Status: Open
   • Created: 3 days ago
   • Description: Messages in the push_sync queue are truncated when close to 1MB, causing stalls.

5. Issue #8154: Node JS - Memory leak

   • Priority: Bug
   • Status: Open
   • Created: 3 days ago
   • Description: Memory leaks observed in Node.js processes affecting performance.

6. Issue #8153: Duplication of screen to filter on entity type

   • Priority: Bug
   • Status: Needs Triage
   • Created: 3 days ago

7. Issue #8152: Auto-save feature in report content editor is not paused while typing

   • Priority: Bug
   • Status: Needs Triage
   • Created: 3 days ago

8. Issue #8151: Upgrade CKeditor to latest version

   • Priority: Feature
   • Status: Open
   • Created: 3 days ago

9. Issue #8150: [Retention policy] Entities are not deleted

   • Priority: Bug
   • Status: Needs Triage
   • Created: 3 days ago

10. Issue #8149-#8100 (various) include questions about LDAP configuration issues and bugs related to user management and UI inconsistencies.

Summary of Recent Activity

The recent activity highlights a mix of critical bugs that could impact user experience and data integrity alongside feature requests aimed at enhancing usability and functionality within the platform. The presence of multiple high-priority issues indicates that while the project is actively developed, there are significant challenges that need addressing to ensure stability and user satisfaction.

Report On: Fetch pull requests

Overview

The OpenCTI project currently has 61 open pull requests (PRs), with a variety of changes proposed across both frontend and backend components. The PRs cover a wide range of topics, including documentation updates, feature enhancements, bug fixes, and dependency updates.

Summary of Pull Requests

1. PR #8161: docs: update README.md

   • State: Open
   • Significance: Minor documentation change correcting "Github" to "GitHub".

2. PR #8160: [frontend] Add page titles to Settings pages and convert to functional components

   • State: Open (Draft)
   • Significance: Enhances user experience by adding titles to settings pages and converting class components to functional ones. Notably, there is a known issue with title rendering.

3. PR #8158: [backend/frontend] massive delete operations for public dashboard and workspaces (#6509)

   • State: Open (Draft)
   • Significance: Introduces functionality for mass deletion of dashboards and investigations, which could significantly improve user management capabilities.

4. PR #8141: [frontend] Change light theme accent (#8129)

   • State: Open
   • Significance: Aesthetic change to the theme, potentially impacting user interface consistency.

5. PR #8140: [backend] Rework error in case of interceptor to prevent HTML default page (#7696)

   • State: Open
   • Significance: Improves error handling in the backend, enhancing robustness.

6. PR #8137: Left Nav Menu Changes

   • State: Open
   • Significance: UI/UX improvement by modifying the left navigation menu's appearance.

7. PR #8135: [backend] Be able to use Vulnerability specific fields in playbook filters (#7409)

   • State: Open
   • Significance: Adds new filtering capabilities for vulnerabilities, enhancing the analytical power of the platform.

8. PR #8133: [frontend] fix hash check search bulk

   • State: Open
   • Significance: Bug fix improving search functionality in bulk operations.

9. PR #8131: Drafts POC (#7393)

   • State: Open (Draft)
   • Significance: Initial work on draft functionality, indicating ongoing development efforts.

10. PR #8121: Popover Removal - Cases

    • State: Open (Draft)
    • Significance: UI change aimed at streamlining user interactions with cases.

11. PR #8119: [backend] Improve redis sessions list perf (#7943)

    • State: Open
    • Significance: Performance improvement for session management in Redis.

12. PR #8114: [frontend/backend] Create public dashboards from dashboard list pages (#6509)

    • State: Open
    • Significance: Enhances dashboard management capabilities by allowing creation from existing lists.

13. PR #8108: Update dependency eslint to v9

    • State: Open
    • Significance: Dependency update that may introduce new linting rules or features.

14. PR #8106-#8052 (various):

    • A series of PRs addressing UI improvements, backend performance enhancements, bug fixes, and dependency updates.

15. Several PRs related to floating action button replacements across various entity types, indicating a broader effort to standardize UI components.

Analysis of Pull Requests

Themes and Commonalities

The current set of open pull requests reflects a diverse range of focus areas within the OpenCTI project:

1. UI/UX Improvements: Many PRs aim to enhance the user interface, including changes to navigation menus, page titles, and floating action buttons. This indicates an ongoing commitment to improving user experience through consistent design patterns and responsive interfaces.

2. Feature Enhancements: Several PRs are dedicated to adding new functionalities such as mass deletion operations for dashboards and improved filtering capabilities for vulnerabilities. This suggests that the project is actively evolving to meet user needs and adapt to changing requirements in threat intelligence management.

3. Bug Fixes and Performance Improvements: A notable number of PRs address existing issues or performance bottlenecks, particularly in session management with Redis and error handling in the backend. This focus on stability is crucial for maintaining user trust and ensuring reliable operations.

4. Documentation Updates: Minor but important changes like updating README files reflect an awareness of the importance of clear documentation for users and contributors alike.

5. Dependency Management: The project is actively managing its dependencies by updating libraries such as ESLint and UUID, which is essential for security and compatibility with modern development practices.

Anomalies

• The presence of multiple draft PRs suggests that contributors are still in the process of refining their changes before submission for review.
• Some PRs have been open for an extended period without significant activity or resolution, which could indicate bottlenecks in the review process or resource allocation challenges.
• There are several instances where PRs are marked as "do not merge," indicating caution around certain changes that may require further testing or validation before integration into the main codebase.

Lack of Recent Merge Activity

While there are numerous open PRs, recent merge activity appears limited compared to the volume of contributions being proposed. This could be due to several factors:

• Resource constraints within the development team may be slowing down review processes.
• The complexity or potential impact of some changes might necessitate more thorough scrutiny before approval.
• Contributors may be awaiting feedback on their drafts before proceeding further with their submissions.

Conclusion

The current landscape of pull requests in the OpenCTI project demonstrates a vibrant community actively contributing towards enhancing functionality, improving user experience, and maintaining system stability through bug fixes and performance optimizations. However, attention should be given to managing review workloads effectively to ensure timely integration of valuable contributions while maintaining high-quality standards across all changes made to the codebase.

Report On: Fetch commits

Repo Commits Analysis

Development Team and Recent Activity

Team Members and Their Recent Activities

1. Julien Richard (richard-julien)

   • Recent activity includes multiple commits focusing on backend improvements, particularly in the ingestion and session management areas. Notably, he introduced a new command for ingestion and made adjustments to session handling to prevent event loop blocking.
   • Collaborated with other team members on various branches.

2. Adrien Servel (Kedae)

   • Active contributor with 42 commits in the last month, addressing both frontend and backend issues. Recent work includes adding forgotten feature flags, fixing UI issues, and enhancing various components across the platform.
   • Collaborated with multiple team members including Julien Richard and Celine Sèbe.

3. Francois GRUNERT (frapuks)

   • Contributed 27 commits focusing on frontend improvements, including refactoring components and fixing bugs related to user settings and capabilities.
   • Worked closely with other developers like Adrien Servel on overlapping issues.

4. Landry Trebon (lndrtrbn)

   • Made 38 commits primarily focused on frontend enhancements, including improving data tables and fixing UI alignment issues.
   • Engaged with other team members on various features and bug fixes.

5. Laurent Bonnet (labo-flg)

   • Contributed 7 commits with a focus on frontend changes, particularly in improving user experience across different components.
   • Collaborated with other developers on UI-related tasks.

6. Samuel Hassine (SamuelHassine)

   • Involved in 27 commits, focusing on backend functionalities such as user management and organizational capabilities.
   • Worked independently but also collaborated with multiple team members.

7. Valentin Bouzin (ValentinBouzinFiligran)

   • Contributed 12 commits mainly addressing backend issues related to indicators and relationships.
   • Collaborated with other developers on specific tasks.

8. Céline Sèbe (CelineSebe)

   • Active in making 32 commits focusing on both frontend and backend improvements, particularly around user settings and organization sharing capabilities.
   • Collaborated with various team members on overlapping issues.

9. Marie Flores (marieflorescontact)

   • Made 12 commits focused on backend testing and user management functionalities.
   • Worked closely with Samuel Hassine and others.

10. Jeremy Cloarec (JeremyCloarec)

    • Contributed 23 commits primarily focused on backend migrations and improvements.
    • Engaged in collaborative efforts with other developers.

11. Gwendoline Favre-Felix (Gwendoline-FAVRE-FELIX)

    • Recently active with several contributions focused on frontend improvements, particularly around attack patterns and translations.

12. A. Jard (aHenryJard)

    • Contributed to CI/CD processes and made several fixes related to e2e testing frameworks.

Patterns, Themes, and Conclusions

• Active Collaboration: The development team exhibits strong collaboration across various branches, often co-authoring commits which indicates a healthy team dynamic.
• Focus Areas: Recent activities highlight an emphasis on both frontend enhancements for user experience and backend stability through improved session management and ingestion processes.
• Feature Flags: Several recent commits involve the addition of feature flags, suggesting ongoing efforts to implement new features while maintaining existing functionalities.
• Testing Improvements: There is a notable focus on improving testing frameworks, indicating a commitment to maintaining code quality through rigorous testing practices.
• Diverse Contributions: The variety of contributions from different team members across multiple branches reflects a well-distributed workload within the team, allowing for simultaneous progress on different aspects of the project.

Overall, the development team is actively engaged in enhancing the OpenCTI platform through collaborative efforts that span both frontend and backend improvements while ensuring robust testing practices are in place.