Skip to content
Tom Bui [SSW] edited this page Apr 20, 2023 · 13 revisions

Welcome to the SSW.CodeAuditor wiki!

1. Why we are using Golang?

2. Is this the correct way to implement rules checking?

  • In accordance with the guidelines set forth by HTMLHint, this represents the precise manner in which regulations for HTML standards are to be implemented.

3. Are there any other libraries which Microsoft have developed which could replace the current HTMLHint

  • To date, we have yet to identify any Microsoft-provided alternatives for conducting static code analysis of HTML.

4. Why we are Firebase?

  • The Firebase interface streamlines server operations and internal functions, resulting in a user-friendly experience that is both efficient and time-saving.
  • With Firebase handling the bulk of operational tasks, developers are afforded the luxury of dedicating additional time towards app development.
  • Firebase offers a rapid means of validating app concepts, allowing for effortless migration to a more robust "enterprise" configuration.

5. Why are some working websites reported as broken in CodeAuditor?

  • After verifying, we discovered that certain websites such as Microsoft and Twitter employ measures against web scraping. These measures may include login authentication or the generation of multiple CORS network errors, as shown in the below screenshot. As a result, although the websites continue to function normally, CodeAuditor labels them as errors in its reports.
  • To address this issue, we propose to exclude these sites from our analysis altogether.

image

Figure: Microsoft website returning CORS network errors

6. CodeAuditor's Architecture Diagram

Untitled Diagram

Figure: CodeAuditor's Architecture Diagram

Clone this wiki locally