search

Be-Secure / BeSLighthouse

Community dashboard for security assessment of open source projects of interest for BeSecure community. Various visualizations on Projects of Interest and Vulnerabilities of interest are available in the dashboard
https://be-secure.github.io/BeSLighthouse/
Apache License 2.0
20 stars 17 forks source link

[Bug]: While displaying onboarded details of dependency projects, weakness column is shown incorrectly. #628

Open sumodgeorge opened 2 months ago

sumodgeorge commented 2 months ago

Contribution guidelines

Description

A bug happened! While clicking on the Rancher dependencies , a pop up window appears displaying the details on dependency projects that were on-boarded onto BeSLighthouse. There is a column for weakness, it was as shown as exist for Boto-3 and Kube-API project when there were no weakness identified for the respective projects.

Expected behaviour

While displaying the dependencies details of an open source project of interest in BeSLighthouse, ensure that the weakness field is populated as exist only if the respective dependency open source project has vulnerabilities / weakness identified against it and the respective details are available in BeSLighthouse. This discrepancy was noticied in Rancher project for now. ALso kindly ensure that the total count of weakness shown for the main project aligns with the details from its dependency projects at all time.s

Actual behaviour

The weakness column for Boto-3 and Kube-API projects were populated as exist even though there are no weakness / vulnerabilities identified for these respective projects.

Steps to reproduce

As a work around, the Boto-3 and Kube-API projects were asked to be deleted from BeSLighthouse. Once it is enabled the issue will be visible.

Relevant screenshots

NA

What browsers are you seeing the problem on?

No response

Relevant log output

No response

samirparhi-dev commented 2 months ago

Surprisingly, few of the data displaying in card seems to be malfunctioned. Kindly have look into it in priority basis. In conjunction to this issue we have created https://github.com/Be-Secure/BeSLighthouse/issues/631 issue , kindly provide or point us to the right documentation.