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		4	8/8/1	15	330	25569
ValentinBouzinFiligran		5	7/5/1	26	108	14894
A. Jard		8	13/9/2	19	143	8744
Marie Flores		4	6/3/1	14	75	4557
renovate[bot]		8	20/17/1	24	11	4523
Landry Trebon		5	5/7/0	22	87	4456
Bonsai8863		1	2/0/0	6	108	3301
Archidoit		10	24/17/1	55	87	2059
Julien Richard		5	4/4/0	22	77	1289
Jeremy Cloarec		6	5/5/0	22	43	1139
Laurent Bonnet		3	3/3/0	25	50	1053
dependabot[bot]		3	12/8/2	10	4	820
Céline Sèbe		3	4/5/0	8	18	774
Souad Hadjiat		2	6/6/0	8	33	765
Samuel Hassine		3	1/1/0	11	72	645
Gwendoline-FAVRE-FELIX		4	3/1/1	13	11	510
Francois GRUNERT		4	4/2/0	18	26	384
Sarah Bocognano		3	2/1/0	7	35	337
Filigran Automation		3	0/0/0	10	4	80
Romy Alula		2	2/2/0	5	5	52
shmztk		1	1/1/0	1	2	37
Gael Leblan		2	1/1/0	2	1	28
Param Constructor		1	1/1/0	1	1	16
troll-os		3	1/1/0	3	1	6
Popa Stefan-Eduard		1	6/1/0	1	1	1
Bruno Gonçalves (bnazare)		0	1/0/0	0	0	0
None (daimyo007)		0	1/0/0	0	0	0
Ikko Eltociear Ashimine (eltociear)		0	0/0/1	0	0	0
KRISHANU NANDI (krish9797)		0	1/0/0	0	0	0
None (VerboseCat)		0	1/0/0	0	0	0
initstring (initstring)		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 seen a significant volume of recent activity with 1,131 open issues, indicating ongoing development and user engagement. Notably, many issues are labeled as "needs triage," suggesting that there may be a backlog of unresolved problems requiring attention.

Several recently created issues highlight recurring themes, such as bugs related to user permissions, UI inconsistencies, and challenges with the CSV import/export functionality. The presence of multiple questions and feature requests also indicates users are actively seeking enhancements and clarifications regarding the platform's capabilities.

Issue Details

Recent Issues

1. Issue #8460: Reverse proxy certificate issue

   • Priority: Bug
   • Status: Needs Triage
   • Created: 0 days ago
   • Description: Incorrect SSL certificate presented when using OpenCTI behind a reverse proxy.

2. Issue #8457: Inability to View Dashboard for All Users

   • Priority: Bug
   • Status: Needs Triage
   • Created: 1 day ago
   • Description: Admin user unable to modify their own dashboard due to permission errors.

3. Issue #8456: Question: CSV null

   • Priority: Question
   • Status: Needs Triage
   • Created: 1 day ago
   • Description: Issues with importing CSV files resulting in null values after an update.

4. Issue #8455: Difference between entity view and relationship view

   • Priority: Question
   • Status: Needs Triage
   • Created: 1 day ago
   • Description: Confusion regarding differing counts in entity and relationship views for the same intrusion set.

5. Issue #8453: Support of "has" relationship between a System and a Vulnerability

   • Priority: Feature
   • Status: Needs Triage
   • Created: 1 day ago
   • Description: Request for a new relationship type to model vulnerabilities associated with systems.

6. Issue #8452: Add filters in file search

   • Priority: Feature
   • Status: Needs Triage
   • Created: 1 day ago
   • Description: Suggestion to enhance file search functionality with additional filters.

7. Issue #8448: Incorrect history leading to non-consistent back in browser

   • Priority: Bug
   • Status: Needs Triage
   • Created: 2 days ago
   • Description: Issues with browser navigation history not functioning correctly.

8. Issue #8446: Add a default confidence level for groups and users

   • Priority: Feature
   • Status: Needs Triage
   • Created: 2 days ago (Edited)
   • Description: Proposal to set default confidence levels to prevent accidental high confidence settings by users.

9. Issue #8445: English grammar errors in the toggle labels for the "Update a group" panel

   • Priority: Bug
   • Status: Needs Triage
   • Created: 2 days ago (Edited)
   • Description: Report on grammatical errors in UI labels affecting clarity.

10. Issue #8442: English grammar errors in the titles of the default dashboard widgets

    • Priority: Bug
    • Status: Needs Triage
    • Created: 2 days ago (Edited)
    • Description: Identified grammar issues in widget titles impacting user experience.

Themes and Commonalities

• Many recent issues revolve around bugs related to user permissions and UI inconsistencies, particularly concerning dashboard functionalities.
• There is a noticeable interest in enhancing CSV import/export capabilities, which is critical for data management within the platform.
• Users are actively engaging with questions about existing functionalities, indicating a need for improved documentation or feature clarity.
• Feature requests suggest an ongoing effort to refine relationships between entities and enhance filtering options within the platform's UI.

This analysis highlights both the active engagement of the OpenCTI community and areas where further development or clarification may be beneficial for users.

Report On: Fetch pull requests

Overview

The analysis of the OpenCTI project's pull requests (PRs) reveals a vibrant and active development environment. The project is continuously evolving, with contributions ranging from dependency updates to significant feature enhancements and bug fixes. The PRs indicate a strong focus on improving user experience, enhancing security features, and expanding the platform's capabilities through new integrations and functionalities.

Summary of Pull Requests

Recent Notable PRs

• PR #8444: Alignment fixes across various components, enhancing UI consistency.
• PR #8441: Changes in how restricted entities are built to prevent API breaks, ensuring stability and reliability.
• PR #8436: Technical improvements by storing enum filter values in constants to avoid hardcoding issues.

Dependency Updates

• PR #8355: Update of @playwright/test to version 1.47.2, ensuring the testing framework is up-to-date with the latest features and fixes.
• PR #8348: Update of opentelemetry-js monorepo, reflecting the project's commitment to maintaining modern and efficient monitoring tools.

Feature Enhancements

• PR #8248: Introduction of pagination for all workbenches, improving data management and accessibility.
• PR #8222: Addition of an AUTO_CREATE_USERS option for Google, GitHub, and Facebook authentication, providing admins with more control over user management.

Bug Fixes and Improvements

• PR #8200: Fixes related to RBAC issues, enhancing security by ensuring proper access controls are enforced.
• PR #8189: Improvements in the CSV parser to handle large volumes of data more efficiently.

Analysis of Pull Requests

Themes and Commonalities

1. Active Maintenance and Improvement: The frequency of PRs related to dependency updates (e.g., PR #8355, PR #8348) indicates a proactive approach to maintaining the project's health and leveraging new features from third-party libraries.

2. User Experience Enhancements: Several PRs focus on improving user experience (e.g., PR #8248 with pagination for workbenches), reflecting an ongoing effort to make the platform more user-friendly and efficient.

3. Security and Stability Focus: PRs like #8441, which addresses potential API stability issues due to changes in how restricted entities are built, highlight a strong emphasis on security and reliability.

4. Feature Expansions: The addition of new features through PRs (e.g., PR #8222 introducing more granular control over user creation via authentication providers) shows an active effort to expand the platform's capabilities.

Anomalies

• The presence of multiple PRs addressing similar areas (e.g., UI enhancements across different components) suggests either overlapping efforts or a coordinated push towards a significant update in those areas. This could indicate effective collaboration among contributors or a need for better coordination to avoid redundancy.

Old PRs and Merge Activity

• The analysis does not highlight any significantly old PRs that remain unmerged, suggesting efficient handling of contributions. However, the presence of draft PRs (e.g., PR #8131) indicates ongoing work that may take time before being ready for merging.

Lack of Recent Merge Activity

• There is no indication of a lack of recent merge activity; in fact, the recent merges (e.g., PR #8444 merged within a day) suggest an active merging process.

Conclusion

The OpenCTI project demonstrates a robust development process characterized by active maintenance, continuous improvement efforts, and a strong focus on expanding its capabilities while ensuring security and stability. The community's engagement through contributions is evident in the diverse range of PRs addressing various aspects of the platform.

Report On: Fetch commits

Repo Commits Analysis

Development Team and Recent Activity

Team Members and Recent Activities

1. Filigran Automation

   • Recent Activity: Released version 6.3.3 and 6.3.2, updating package files across multiple components.

2. Adrien Servel (Kedae)

   • Recent Activity:
   • Fixed global search table.
   • Worked on alignment fixes across multiple frontend components.
   • Collaborated with several team members on various tasks.

3. Jeremy Cloarec

   • Recent Activity:
   • Modified backend logic for restricted entities.
   • Added tests for user management.
   • Collaborated with Marie Flores on user organization checks.

4. Samuel Hassine

   • Recent Activity:
   • Fixed global search table and search functionality in various components.
   • Enhanced dynamic filtering for special instance control.
   • Worked on backend improvements for container creation.

5. Julien Richard (richard-julien)

   • Recent Activity:
   • Improved organization sharing logic.
   • Adapted GraphQL armor options and default values.
   • Collaborated on backend improvements related to session management.

6. Céline Sèbe (CelineSebe)

   • Recent Activity:
   • Enhanced settings panel layout.
   • Fixed breadcrumb navigation in various components.
   • Collaborated with multiple team members on feature flags and UI fixes.

7. Souad Hadjiat

   • Recent Activity:
   • Fixed task widget alignment and infinite scroll issues.
   • Contributed to various frontend fixes.

8. Francois GRUNERT (frapuks)

   • Recent Activity:
   • Implemented fixes across multiple frontend components, focusing on UI/UX improvements.

9. Popa Stefan-Eduard (stefan1anuby)

   • Recent Activity:
   • Fixed scrollbar issues in custom dashboards.

10. A. Jard (aHenryJard)

    • Recent Activity:
    • Updated dependencies and fixed CircleCI workflows.

11. Marie Flores (marieflorescontact)

    • Recent Activity:
    • Worked on user organization checks and added tests for user management.

12. Valentin Bouzin (ValentinBouzinFiligran)

    • Recent Activity:
    • Made various updates to translations and entity creation forms.

13. Landry Trebon (lndrtrbn)

    • Recent Activity:
    • Focused on UI improvements and bug fixes across multiple frontend components.

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

    • Recent Activity:
    • Addressed translation issues and fixed errors in frontend components.

15. Sarah Bocognano (SarahBocognano)

    • Recent Activity:
    • Contributed to enhancements in the knowledge tab for various entities.

Patterns, Themes, and Conclusions

• The team is actively releasing new versions of the software, indicating a strong focus on continuous improvement and feature enhancement.
• Collaboration is evident among team members, particularly in fixing bugs and enhancing UI/UX elements across the platform.
• A significant amount of work is being done on both frontend and backend components, with a balanced distribution of tasks among team members.
• The presence of multiple contributors working on similar features suggests a collaborative environment aimed at improving the overall quality of the software.
• Recent activities show a focus on fixing existing issues while also introducing new features, reflecting a commitment to both stability and innovation within the project.

Overall, the development team demonstrates a proactive approach to maintaining and enhancing the OpenCTI platform, with effective collaboration leading to consistent progress across various aspects of the project.