NIST-BRSKI policy app using claim cascade system

[A9-dev]

Setup

Install node dependencies with npm i in /packages/cahn_demo/client and /packages/cahn_demo/server.

Run the client in /packages/cahn_demo/client with npm run dev. Run the server in /packages/cahn_demo/server with npm run dev.

(Sorry, couldn't get npm workspaces to work for some reason)

Ensure you have populated the /packages/cahn_demo/server/.env file, according to the template found in /packages/cahn_demo/server/.env_example.

Notes

There is much clean up to be done with this code. However, it should be functionally correct.

[A9-dev]

Changes

• Styled table component
• Schemas are accessible to the client (/client/src/schemas, publishing to npm felt overkill)
• Made changes to manufacturer_trust schema to homogenise naming, used in sorting function
• Trust VCs are built using the schema
• TrustSubmissions component
• Removed WASM initialisation function duplication

Notes

• Other functions could be extracted, like the handleSubmitTrust for each page, but since they do slightly different things I'm on the fence whether it's better practice and safer to keep them separated or to make one more complicated function with more parameters like the endpoints used within the function.