You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The misp-stix utilizes misp-lib-stix2, a fork derived from the stix2 project. Challenges arise when concurrently employing pymisp, which relies on the official stix2 package. Notably, conflicts emerge due to the identical naming of the stix2 module in both misp-stix and pymisp
Describe the solution you'd like
In order to address the naming conflicts, I propose updating the stix2 module to misp_lib_stix2. This adjustment has been formalized through a pull request, which can be reviewed at PR #3 within the misp-lib-stix2 repository. Once this modification is merged, I intend to submit a subsequent pull request for misp-stix, ensuring compatibility with the refined module name, misp_lib_stix2. This solution aims to harmonize the integration of both packages seamlessly. Your consideration of this proposed resolution is greatly appreciated.
Describe alternatives you've considered
No response
Additional context
Let me know if we can take any other way.
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
The misp-stix utilizes misp-lib-stix2, a fork derived from the stix2 project. Challenges arise when concurrently employing pymisp, which relies on the official stix2 package. Notably, conflicts emerge due to the identical naming of the stix2 module in both misp-stix and pymisp
Describe the solution you'd like
In order to address the naming conflicts, I propose updating the stix2 module to misp_lib_stix2. This adjustment has been formalized through a pull request, which can be reviewed at PR #3 within the misp-lib-stix2 repository. Once this modification is merged, I intend to submit a subsequent pull request for misp-stix, ensuring compatibility with the refined module name, misp_lib_stix2. This solution aims to harmonize the integration of both packages seamlessly. Your consideration of this proposed resolution is greatly appreciated.
Describe alternatives you've considered
No response
Additional context
Let me know if we can take any other way.
Code of Conduct
The text was updated successfully, but these errors were encountered: