loconous / dre Goto Github PK

Revamp VulnerabilityResultsForm to display VulnerabilityResultsHeader. Update VulnerabilityResultsPage to reflect changes. Add preparation containers for results summary to list details for authors, projects, commits, and blobs.

Set up ssh for da0, da2, and docker on local machine. Got website to run on localhost

We need to finish assimilating api/vulnerability.js to be able to call the shared/vulnerability.js file

Create route path "/vulnerabilityresult" to VulnerabilityResultPage within index.js.

We need to link the express validation that is required to make our middleware validation work

Create VulnerabilityStatCard.js to display four "cards" on the VulnerabilityResultsPage. Each "card" provides total number of commits, authors, deforked projects, and project results. This will be hooked in with a "dummy" .json file until backend is connected.

ConceptDrawing_Version_1_0.pdf

I am working a process_container element that will store the status of the recent search. It is to show the name of the project searching for and the status of the search. If the status is set to working, then the user will have the ability to cancel the search if it is taking too long, and if the status is set to finished, then the user can open the search results.

Go to fontawesome to select an icon for vulnerability search in the header. Change this is header.js

In the processes of updating the search form, I created a new inputbox that looks like the one in the concept drawings.

Create two new "tester" .json files to display results for vulnerability results summary. The "tester" files will assist backend formatting for connection. The file array.json contains data for blobs and number of authors, projects, and commits. The file author.json contains authors as keys then links it to its project and commit details.

Add Accordion to display blobs, author, and their details in an organized manner. Nest accordions to drop down additional details to aid in sorting through the results. Originally a table format was used and the data did not achieve the desired organization I was looking for. Output was redone with a nested accordion. Organized by Blobs > Authors > Project/commit details.

Import/connect test results from .json file. Update displayed text, icon, and color for each VulnerabilityStatCard. Display "test" results for each "card": commits, author, deforked projects, total projects.

Set up axios for vulnerability search page and return something

Create a new link in the header that routes to the vulnerability search page

Create VulnerabilityStyles.js to determine table display properties

Retrieve project name data from dummy json file and display it in a card view on the vulnerability results page

Create VulnerabilityResultsHeader.js file which utilizes VulnerabilityStatCard to display results. The /vulnerabilityresult page will display each "card" providing total number of commits, authors, deforked projects, and project results. This will be hooked in with a "dummy" .json file until backend is connected.

Create VulnerabilityStatTable component to display results. Takes in two test .json files. Loops through array of vulnerability results data and parses blob, authors count, project count, commits count, and authors list to display on /vulnerabilityresults page. Compares to second .json file of authors to display their corresponding project and commit details.

Import VulnerabilityStatTable to VulnerabilityResultForm.js to display on /vulnerabilityresult page. Pass data such as lookup results for blob contents, list of authors and corresponding project/commit details, blob details, and title for use in VulnerabilityStatTable.js.

Set up ssh for da0, da2, and docker on local machine. Got website to run on localhost

Create VulnerabilityStatTable.js file to display results summary for vulnerability search. Includes all blobs, authors, and its details found in the search. Uses dummy json file and should be connected to backend in the future.

Merge woc-tools from Prof. David to DRE and set up for usage of search app

I have been updating the search form, so that it has same style as the ConceptDrawings. While concept is still in the working, it has the general idea of what needs to be developed.

Add onClickBlob function in VulnerabilityStatTable.js that utilizes Lookup to display blob details as pop up. When the user clicks the blob sha rather than the accordion, a pop up of the blob content is displayed by using the information returned from lookup sha function of WoC.

Create "dummy" data.json file to import test results into VulnerabilityResultsForm. The test data will be passed to the VulnerabilityResultsHeader to display as results for the four "cards": commits, authors, deforked projects, and total projects.

Create a README.md within our Vulnerability search project folder to document about our project and how it can be used up. This may include a standard MIT license as recommended in class - either as a separate file or within the README.md.

1. Register for WoC hackathon to receive credential info
2. Complete WoC tutorial
3. Fork DRE repository for app development
4. Meet with Dylan to set up ports for team and access development environment

Import "bootstrap" in package.json for desired properties for the blob summary results. Styles used for accordion in VulnerabilityStatTable.js. Rather than the VulnerabilityStyles.js that was intended for the table properties, the bootstrap styles for the accordion were used.

Create vulnerability search form. Create search bar and search button.

We need to create a middleware vulnerability file in the same that lookup uses it for validation. The file will be called vulnerabilityValidate.js

Have results from vulnerability search link to the vulnerability search page