How muhammadiishaq/tws-shop-with-devsecops-github-action works
TWS-Shop is a static e-commerce storefront served by a small Express application. A visitor requests the home or product page; the server returns the corresponding HTML and serves public assets. Browser-side modules provide cart, menu, and theme behavior. The README also presents a GitHub Actions DevSecOps pipeline as a project capability, including image publication, scanning, and deployment. Its workflow implementation was not sampled, so those links reflect README statements rather than inspected workflow code.
Main entry points: server.js Express Server · devsecops-pipline-final.yml CI/CD Workflow · index.html Home Page · product.html Product Page
Components 13
Storefront
- Home Page
views/index.html - Product Page
views/product.html - Static Assets
public - Storefront Styling
public/css/style.css - Cart Behavior
public/js/cart.js - Menu Behavior
public/js/menu.js - Theme Behavior
public/js/theme.js
Web Server
- Express Server
server.js
DevSecOps
- CI/CD Workflow
.github/workflows/devsecops-pipline-final.yml
Other components
- Shopper
- GitHub Actions
- Docker Hub
- Production Server
Connections 7
- Shopper → Express Server: requests pages
server.js - Express Server → Home Page: serves /
server.js - Express Server → Product Page: serves /product
server.js - Express Server → Static Assets: serves static files
server.js - GitHub Actions → CI/CD Workflow: runs workflow
README.md - CI/CD Workflow → Docker Hub: publishes image
README.md - CI/CD Workflow → Production Server: deploys with Compose
README.md