Retire HTTP API as datasource for cvexplore

[P-T-I]

Open question; is the HTTP API as a datasource still needed or can we retire this funcitonality in light of the #213 roadmap

[baonq-me]

What do you mean by "retire"?

[P-T-I]

Remove... CveXplore is able to use the cvesearch query api endpoint as a datasource; but for me (looking at the new design) this is no longer a viable option as it feels like going in circles...

[baonq-me]

Remove... CveXplore is able to use the cvesearch query api endpoint as a datasource; but for me (looking at the new design) this is no longer a viable option as it feels like going in circles...

@P-T-I What do you think about my below idea?

Based on what I have analyzed previously about three use cases:

For the first group of people who want to use CLI. I know many CLI tools use this approach. We can host a public demp instance of cve-search-api so people don't need to deploy anything except CveXplore (or they can deploy their own instance otherwise if needed).

For the second group of people who want to use every component:

For the third group of people who care about integrations rather than GUI:

Another thing to consider is that cve-search is currently having 2.1K stars, so people will likely want to contribute to that project more than a new and fewer stars project. Of course, we can split cve-search into two seperate folders, for example, cve-search-frontend and cve-search-api.

[P-T-I]

@baonq-me FYI there is a public instance (https://cvepremium.circl.lu) and yes, the first use case you described is exactly where I designed cvexplore for; for people who just want to download the lib and use the public instance as a data source. So I think we can agree that we'll keep that as is.

I don't believe splitting up the CveSearch rest api from the frontend source code would lead to much benefit. So only the CLI functionality would be fased out (in due time) from the CveSearch repo.

[P-T-I]

I believe this issue can be closed; feel free to reopen if needed!