Demo mode, read-only. Request a demo →

Readiness report · Sample app (fictional)

BrightPath Tutoring

Critical 1

Critical AUTH-01 A password is checked against a value written into the code Sign-in and access server.js:50

AI-generated

Why it matters. The admin password is written directly into server.js, so anyone with access to that code can see the value used for the check. Changing it also requires changing the code.

Fix. Replace the embedded password with a salted password hash supplied through an environment variable and stored in AWS Secrets Manager. Use a password-verification library with constant-time comparison and choose a new admin password before launch.

Evidence. Compared with a literal: …2024 (21 characters)

48// Admin view for the tutors.49app.get("/admin", (req, res) => {50  if (req.query.password !== "…2024") {51    return res.status(401).send("Wrong password");52  }

High 2

High DATA-01 A JSON or CSV file is used as the database Data storage server.js:23

AI-generated

Why it matters. Bookings are saved to a local JSON file rather than a managed database. Without separate persistent storage and backups, replacing the container could lose bookings.

Fix. Move booking records to Amazon RDS or DynamoDB and enable backups. Import any existing bookings before switching the app over.

Evidence. fs.writeFileSync(BOOKINGS_FILE, JSON.stringify(bookings, null, 2));

2122function saveBookings(bookings) {23  fs.writeFileSync(BOOKINGS_FILE, JSON.stringify(bookings, null, 2));24}25
High DEP-01 lodash 4.17.15 has 5 known security advisories Dependencies package.json:12

AI-generated

Why it matters. The scanner lists five published security advisories for the lodash version in package.json. Keeping that version leaves known weaknesses in the app's dependencies.

Fix. Upgrade lodash to 4.18.0 or later and update the dependency lock file. Re-test booking creation, occupied-slot checks and the admin booking list.

Evidence. GHSA-29mw-wpgm-hmr9, GHSA-35jh-r3h4-6jhm, GHSA-p6mc-m468-83gw, GHSA-r5fr-rjxr-66jc, GHSA-xxjr-mmjv-4gpg. First fixed version: 4.18.0

10    "cors": "2.8.5",11    "express": "4.21.2",12    "lodash": "4.17.15"13  }14}

Medium 2

Medium DATA-02 The app collects personal data: phone numbers Data storage public/index.html:16

AI-generated

Why it matters. The booking form collects phone numbers alongside student names and parent emails. This personal information needs clear handling rules and restricted access.

Fix. Collect only the details you need, explain their purpose and retention period, and delete them when no longer needed. Store records encrypted in a managed database and limit access to authorized staff.

Evidence. Fields found: phone numbers

14      <label>Student name <input name="student" required></label>15      <label>Parent email <input name="parentEmail" type="email" required></label>16      <label>Phone <input name="phone" type="tel"></label>17      <label>Subject18        <select name="subject"><option>Math</option><option>Reading</option><option>Science</option></select>
Medium AUTH-02 Nothing slows down repeated password guesses Sign-in and access server.js:50

AI-generated

Why it matters. The admin password check has no limit on repeated attempts. Anyone who can reach the address could automate password guesses.

Fix. Temporarily block further attempts after a small number of failures, such as five failures for 15 minutes. Configure the app to use the visitor address supplied by your trusted AWS load balancer, rather than trusting arbitrary forwarded addresses.

Evidence. No rate limiting or lockout found for sign-in

48// Admin view for the tutors.49app.get("/admin", (req, res) => {50  if (req.query.password !== "…2024") {51    return res.status(401).send("Wrong password");52  }

Low 2

Low CFG-01 Any website is allowed to call this app's API (CORS *) Configuration server.js:12

AI-generated

Why it matters. The code allows browser pages from any website to call and read responses from the app's API. That is broader access than this booking site appears to need.

Fix. Replace the unrestricted CORS setting with an explicit list of your approved website addresses. Treat this as a browser restriction, not a replacement for password protection.

Evidence. app.use(cors());

10const BOOKINGS_FILE = path.join(__dirname, "data", "bookings.json");1112app.use(cors());13app.use(express.json());14app.use(express.urlencoded({ extended: true }));
Low OPS-02 No health check address Deployability server.js

AI-generated

Why it matters. The code has no dedicated health-check address. A simple endpoint gives AWS a predictable way to check whether the app is responding.

Fix. Add the supplied /health route before app.listen. Configure the AWS load balancer to check that path on port 8080 and expect HTTP 200.

Evidence. No /health route found

Info 1

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

AI-generated

Why it matters. The project has no Dockerfile to define how it should be packaged and started on AWS. A consistent container setup makes deployment repeatable.

Fix. Add the supplied Dockerfile and .dockerignore, then build and test a linux/amd64 image. Confirm that the app responds on port 8080 before deploying it.

Evidence. No Dockerfile in the project