Currently, the components on the front end seem a little disorganized.

Organize the components in a good structure.

come up with a structure as part of this issue

The following sections of code needs testing

1. Server APIs
2. Client Components needs to be tested

The Codebase currently has an unconventional setup.

Explore turborepo and create a nice abstraction of packages and applications

List of packages required

1. Schema
   • Should host all the shareable type script definitions and be able to publish the declaration file across packages and apps
   • Should not contain any isolated types
2. UI
   • Should host all the necessary UI components that can be shared between packages and apss
   • Should contain the necessary third-party tools inside the packages
3. Scanner
   • Scanner package should contain the APIS for different packages and apps
   • Should be able to consume schemas from Schema package
   • Scanner should have the ability to support the following environments/APPS
     • Web
     • CLI
     • API driven APPs

Create CI and CD pipelines in github

CI

Check

1. Lint the code with es lint
2. Run the tests for coverage
3. Type-check the code base
4. Commit message linter (nice to have)

Build

1. Creates the production build of
   • Server
   • Client

CD

Release

1. Create a versioned release with semantic releases
2. Publish the release to NPM

Deploy

1. TBD