Nex Site Trust Ext

The problem

Building a Chrome extension from scratch involves navigating Manifest V3 manifest requirements, service worker lifecycles, and cross-script communication. Most scaffolds are either empty or require complex build pipelines just to see a "Hello World" in the browser.

What it does

• Generates a complete, production-ready Manifest V3 extension using vanilla JS, HTML, and CSS.
• Calculates a 0 to 100 trust score based on SSL status, domain age via RDAP, and transparency signals like privacy policies and return info.
• Includes a content script that injects on-page warnings for high-risk domains.
• Provides a settings dashboard for user-supplied Google Safe Browsing and PhishTank API keys.
• Implements local storage persistence for settings and extension state without a backend.

Frameworks & tools

Chrome Extension Manifest V3, Vanilla JavaScript, HTML5, CSS3, RDAP API, Google Safe Browsing API, PhishTank API.

Why this beats prompting it yourself

This is the actual source code of a shipped extension. It solves the non-trivial task of coordinating background service workers, content scripts, and popup UI without a build step. You get a working security engine and asset structure that follows Chrome Web Store requirements out of the box.

Use cases

• Deploy a website safety checker to protect users from phishing and scams.
• Fork the codebase to build any "action-on-click" style toolbar extension.
• Learn Manifest V3 architecture by studying a working, multi-part implementation.
• Create a tool that scrapes and analyzes site metadata in real-time.

Known limitations

This skill uses the vanilla no-build pattern. It is not compatible with React, Vue, or TypeScript build pipelines without manual migration.