greenlitlab
Related Servers
Alternatives to greenlitlab
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceSecurity checks for apps built with AI coding tools (Lovable, Bolt, Cursor, Claude Code). Scans a public GitHub repo for open Supabase tables, exposed keys, unprotected server functions and unverified webhooks, and returns each finding with the file and a fix prompt.2419 npmMIT
- AlicenseAqualityCmaintenanceEnables AI agents and developers to audit any URL or domain for seven critical OWASP HTTP security headers, returning an A+ to F grade plus actionable Nginx, Apache, Caddy, and Cloudflare remediation snippets. It also probes /.well-known/security.txt and /security.txt to surface responsible vulnerability disclosure contacts, bug bounty scopes, and PGP keys.2MIT
- AlicenseNot gradedqualityBmaintenanceEnables grading a website's security headers with per-gap fixes and a README badge, and analyzing logs, code, configs or suspicious messages to determine what happened, how severe it is, and what to fix first. Requests are masked for sensitive data and automatically retried across multiple AI providers when one refuses, subject to a defensive-use-only policy.1MIT
- AlicenseAqualityBmaintenanceScan a deployed site for an exposed Supabase service_role key and audit Row Level Security from your AI coding agent.2460 npmMIT
- AlicenseNot gradedqualityCmaintenanceScans an app's source files and a read-only Supabase catalog snapshot to surface security holes such as exposed tables, missing row-level security, overly broad policies, leaked service-role keys, and unauthenticated API routes, returning fixes for each and confirming after a change which issues actually closed.MIT
- AlicenseAqualityDmaintenanceAudit any website for privacy, security, accessibility, and performance issues — with scores, grades, and actionable fix instructions. No account required.3MIT
TDQS
Scored across 4 tools
Each tool has a clearly distinct input source and scope: local project files (greenlit_scan), Supabase advisor lints passed in (greenlit_advisor), owner-only answers (greenlit_questions), and a live deployed URL (greenlit_check). The descriptions explicitly delimit boundaries, e.g. scan covers what 'can't be seen from outside' while check covers 'what the site serves to every visitor', so an agent can pick correctly.
All four names share a uniform greenlit_ prefix with a single short lowercase suffix, giving a predictable pattern. Minor deviation: suffixes mix verbs (scan, check) and nouns (advisor, questions), so it isn't a strict verb_noun convention, but it remains consistent and readable.
Four tools for a focused launch-readiness audit product is well-scoped, with no redundant entries. It sits at the lean end of the 3-15 range, but each tool earns its place and none could be merged without losing a distinct input channel.
The surface covers the main launch-check layers: local code, external deployed site, database advisor lints, and owner-attested operational questions, each returning findings with fix prompts. Minor gaps exist, such as no consolidated report tool that aggregates findings across all four checks or persists results between runs beyond the per-run change diff.