How prateek-chaubey/websafe works
SaferWeb is an Express URL-security service with a browser-served page and three documented capabilities: URL threat checks, screenshot capture, and proxified browsing. The main workflow checks a URL, follows its redirects, and submits the final URL to Google Safe Browsing; the same service also offers screenshot and proxy endpoints. The README documents URL expansion and redirect tracking, but no separate expansion endpoint appears in the sampled runtime. The graph is based on the README and index.js; unsampled page behavior is not inferred.
Main entry points: index.js Express server · index.html Web interface
Components 11
HTTP service
- Express server
index.js - Web interface
index.html
URL security
- Safety endpoint
index.js - Redirect resolution
index.js - Threat lookup
index.js - Google Safe Browsing
Website access
- Screenshot endpoint
index.js - Headless browser
index.js - Proxy endpoint
index.js - Target website
Other components
- Browser user
Connections 11
- Browser user → Express server: requests endpoints
README.md - Express server → Web interface: serves page
index.js - Express server → Safety endpoint: routes safety checks
index.js - Express server → Screenshot endpoint: routes captures
index.js - Express server → Proxy endpoint: routes proxy access
index.js - Safety endpoint → Redirect resolution: fetches and follows
index.js - Safety endpoint → Threat lookup: checks final URL
index.js - Threat lookup → Google Safe Browsing: submits threat query
index.js - Screenshot endpoint → Headless browser: captures page
index.js - Headless browser → Target website: loads page
index.js - Proxy endpoint → Target website: forwards requests
index.js