How chandakasaikiran54-source/food-safety works
FoodSafe AI provides user and officer workflows for food-image assessment, assessment history and feedback, restaurant inspections, and complaints. The main flow is a user submitting an image through the web app; the backend routes the request to an AI service, persists an assessment, and returns it for display. Tomato and microbial analysis are distinct assessment capabilities, alongside raw-food and general scans. Source excerpts establish key backend-to-AI and persistence calls; several page-to-API and unsampled feature links are therefore omitted or marked unverified.
Main entry points: server.js API server · App.jsx Web routes · api.js HTTP client · Scan.js MongoDB models
Components 22
Web application
- Web routes
frontend/src/App.jsx - Session context
frontend/src/context/AuthContext.jsx - Food scan pages
frontend/src/pages/ScanFood.jsx - Raw food pages
frontend/src/pages/RawFoodScan.jsx - Tomato pages
frontend/src/pages/TomatoAnalysis.jsx - Microbial pages
frontend/src/pages/MicrobialAnalysis.jsx - Inspection pages
frontend/src/pages/InspectionForm.jsx - HTTP client
frontend/src/utils/api.js
Backend API
- API server
backend/server.js
Food assessment
- Food scan handler
backend/controllers/scanController.js - Raw food handler
backend/controllers/rawFoodController.js - Tomato handler
backend/controllers/tomatoController.js - Microbial handler
backend/controllers/microbialController.js - Image analysis API
ai-service/app.py - Tomato analysis
ai-service/food_analyzers/tomato.py - Microbial detection
ai-service/microbial/microbial_detector.py
Safety oversight
- Restaurant records
backend/controllers/restaurantController.js - Officer workflows
backend/controllers/officerController.js - Complaint handling
backend/controllers/complaintController.js
Assessment data
- MongoDB models
backend/models/Scan.js
Other components
- User
- Officer
Connections 34
- User → Web routes: uses
frontend/src/App.jsx - Officer → Web routes: uses
frontend/src/App.jsx - Web routes → Session context: provides session
frontend/src/App.jsx - Web routes → Food scan pages: routes to
frontend/src/App.jsx - Web routes → Raw food pages: routes to
frontend/src/App.jsx - Web routes → Tomato pages: routes to
frontend/src/App.jsx - Web routes → Microbial pages: routes to
frontend/src/App.jsx - Web routes → Inspection pages: routes to
frontend/src/App.jsx - Session context → HTTP client: requests
frontend/src/context/AuthContext.jsx - Food scan pages → HTTP client: submits scan
- Raw food pages → HTTP client: submits image
- Tomato pages → HTTP client: submits images
- Microbial pages → HTTP client: requests analysis
- Inspection pages → HTTP client: requests records
- HTTP client → API server: calls API
- API server → Food scan handler: mounts routes
backend/server.js - API server → Restaurant records: mounts routes
backend/server.js - API server → Officer workflows: mounts routes
backend/server.js - API server → Complaint handling: mounts routes
backend/server.js - API server → Raw food handler: mounts routes
backend/server.js - API server → Tomato handler: mounts routes
backend/server.js - API server → Microbial handler: mounts routes
backend/server.js - Food scan handler → Image analysis API: posts image
backend/controllers/scanController.js - Raw food handler → Image analysis API: posts image
backend/controllers/rawFoodController.js - Tomato handler → Image analysis API: requests analysis
backend/controllers/tomatoController.js - Image analysis API → Tomato analysis: uses analyzer
ai-service/app.py - Image analysis API → Microbial detection: uses detector
ai-service/app.py - Food scan handler → MongoDB models: stores scans
backend/controllers/scanController.js - Raw food handler → MongoDB models: stores assessments
- Tomato handler → MongoDB models: stores assessments
- Microbial handler → MongoDB models: stores results
- Restaurant records → MongoDB models: reads records
- Officer workflows → MongoDB models: uses records
- Complaint handling → MongoDB models: stores complaints