Demo mode, read-only. Request a demo →

Readiness report · Sample app (fictional)

Sweet Crumb Bakery

Critical 1

Critical SEC-01 Google API key written into the code, in a file sent to the browser Secrets index.html:37

AI-generated

Why it matters. The Google API key written in index.html is included in files sent to the browser, so it is not private. If the key is active and insufficiently restricted, someone could use it against your Google account and generate charges. Anyone visiting your site can read this.

Fix. Replace the exposed key and restrict its replacement in Google Cloud to your production website domains and only the Maps APIs you need. Keep any server-only keys out of website files entirely.

Evidence. Google API key: AIza…0000 (38 characters)

35  <!-- Google Maps for the "Visit us" section -->36  <script>37    const MAPS_API_KEY = "AIza…0000";38    const s = document.createElement("script");39    s.src = "https://maps.googleapis.com/maps/api/js?key=" + MAPS_API_KEY + "&callback=initMap";

Medium 4

Medium SEC-02 No .gitignore file, so secrets files can be committed by accident Secrets

AI-generated

Why it matters. The project has no top-level .gitignore to help keep private settings out of saved code history. A future file containing passwords or keys could be committed accidentally.

Fix. Add a top-level .gitignore containing .env and .env.*, with !.env.example to allow the empty settings template. This does not remove files already committed; remove any tracked secret files and replace exposed keys separately.

Evidence. No .gitignore at the top of the project

Medium DATA-01 The app collects personal data: email addresses, phone numbers Data storage order.html:19

AI-generated

Why it matters. The order form asks for email addresses and phone numbers, which need careful handling. The supplied website code does not establish how an order service would store or protect that information.

Fix. Collect only necessary details and explain their use and retention period beside the form. Before accepting orders, arrange encrypted storage in a managed database, restrict staff access and establish a deletion process.

Evidence. Fields found: email addresses, phone numbers

17    <form id="cake-order" action="http://localhost:5000/api/orders" method="post">18      <label>Your name <input name="name" required></label>19      <label>Email <input name="email" type="email" required></label>20      <label>Phone <input name="phone" type="tel"></label>21      <label>Pickup date <input name="pickup_date" type="date" required></label>
Medium CFG-01 The page calls a localhost address that will break once deployed Configuration js/order.js:9

AI-generated

Why it matters. The JavaScript sends orders to localhost, which means the computer running the browser, not your AWS service. On a deployed site, this would send the request to the wrong destination.

Fix. Change the fetch address in js/order.js to /api/orders. Arrange for your production website to route that address to the order service, then test successful and failed submissions.

Evidence. const res = await fetch("http://localhost:5000/api/orders", {

7  const order = Object.fromEntries(new FormData(form).entries());8  try {9    const res = await fetch("http://localhost:5000/api/orders", {10      method: "POST",11      headers: { "Content-Type": "application/json" },
Medium CFG-02 The page calls a localhost address that will break once deployed Configuration order.html:17

AI-generated

Why it matters. The form's own submission address also points to localhost. If the browser submits through this address, it would target the customer's computer rather than your order service.

Fix. Change the action in order.html to /api/orders as well. Ensure the order service supports the form's submission format if this path is intended to work without JavaScript.

Evidence. <form id="cake-order" action="http://localhost:5000/api/orders" method="post">

15    <h1>Order a custom cake</h1>16    <p>Tell us about your celebration and we will confirm by email within one day.</p>17    <form id="cake-order" action="http://localhost:5000/api/orders" method="post">18      <label>Your name <input name="name" required></label>19      <label>Email <input name="email" type="email" required></label>

Info 1

Info OPS-01 No Dockerfile yet (a draft is on the Fixes tab) Deployability

AI-generated

Why it matters. There is no Dockerfile describing how to package and serve the website consistently on AWS. A container definition gives deployment a repeatable starting point.

Fix. Add the supplied Dockerfile and .dockerignore, then build and test the linux/amd64 image. The container serves website files and /health; it does not provide the order service.

Evidence. No Dockerfile in the project