Browser Extension Trust Assessment — assessed in minutes
Regulatory Signals is an independent technical evaluation provider. This product is not an accredited certification under ISO/IEC 17065 or ISO/IEC 17021. Evaluation findings are technical assessments, not regulatory endorsements or legal opinions.
10 extension-specific security rules. Signed assessment report. Public registry listing. Enterprise IT teams use our registry as the source of truth for approved Chrome and Edge AI extensions.
Already audited? · Chrome, Edge, Firefox · Badge for your Web Store listing · Prior art: SOC 2, Snyk
What the Extension Audit fixes
Security Vulnerabilities
The problem
Extensions run inside the browser with access to every page the user opens.
What we find
Remote code loaded at runtime, eval in extension pages, DOM injection through unvalidated messages, message passing with no origin check, and request-interception patterns that can be abused.
Privacy & Liability
The problem
Corporate IT will not allow an extension it cannot vouch for.
What we find
Host permissions wider than the stated purpose, data sent to hosts outside an allowlist, credentials in localStorage, tab capture without consent, and an update server that is not Google-hosted.
Evidence You Can Cite
The problem
IT teams need something they can point to, not a promise.
What we find
Severity ratings mapped to CWE weakness classes, a signed assessment report, a verification endpoint you can cite in an allowlist change request, and a public registry listing.
Getting corporate IT inquiries?
When enterprise buyers ask "do you have a security audit?", the Extension Trust Cert is your answer. Put the gold badge on your Chrome Web Store listing. Close the sale.
$149 one-time audit · results in minutes
Building an extension allowlist?
The Extension Trust Registry gives you an independent, citable security signal for your allowlist change request. Each cert ships with a signed verification JSON endpoint.
Free to search · machine-readable verification JSON
10 extension vulnerability rules
CWE mapped · Chrome Manifest V3 aligned · covers Chrome, Edge, Firefox
CWE-272 · Permissions exceed declared purpose
CWE-79 · Unvalidated postMessage to innerHTML
CWE-200 · Data sent outside declared connect-src
CWE-116 · eval() or new Function() in extension context
CWE-94 · Remote JS injected at runtime
CWE-441 · Request interception with mutation
CWE-312 · Unencrypted sensitive data at rest
CWE-346 · Missing event.origin validation
CWE-352 · Screen/audio capture without visible prompt
CWE-494 · Self-hosted update_url = supply chain risk
Trust badge grades
Score is calculated from weighted rule findings. Each finding includes remediation guidance.
90 or above
Zero critical or high findings. Safe for enterprise deployment.
70 or above
No critical findings. Minor issues documented and tracked.
50 or above
Critical findings present but mitigated with documented controls.
Below 50
Active critical findings with no mitigation. Listing published without badge.
Frequently asked questions
What does a browser extension security audit cover?
10 rules covering: host-permission overreach beyond stated purpose (ext-001), DOM injection via unvalidated message events (ext-002), data exfiltration to non-allowlisted hosts (ext-003), unsafe-eval CSP violation (ext-004), remote code execution via dynamic script loading (ext-005), dangerous webRequest/declarativeNetRequest patterns (ext-006), credential storage in unencrypted localStorage (ext-007), message-passing without origin validation (ext-008), tab capture without explicit user consent (ext-009), and update server not hosted on Google's update infrastructure (ext-010). Each rule is mapped to a CWE identifier.
How long does the extension audit take?
Static analysis of your extension manifest and source runs automatically. The signed assessment JSON and public registry listing are issued automatically when the analysis finishes.
What does the trust certificate include?
A tamper-evident HMAC-SHA256 certificate with: extension slug, Chrome Web Store ID (if applicable), version audited, security score (0–100), trust grade (gold/silver/bronze/none), issuance date, expiry date, and a machine-readable endpoint at /api/extension-cert/{slug} for verification by enterprise IT tools.
Why do corporate IT teams require a trust cert?
IT security teams managing Chrome browser policies have no standardized third-party signal for extension safety — the Extension Trust Cert fills that gap. Each cert includes a signed verification JSON endpoint you can cite in an allowlist change request.
What badge grade will my extension receive?
Gold (score 90 or above): zero critical or high findings. Silver (score 70 or above): no critical findings, minor issues documented. Bronze (score 50 or above): critical findings present but mitigated with documented controls. None (score below 50): active critical findings with no mitigation — listing published without badge.
Corporate IT teams are building allowlists now
Security admins managing Chrome browser policies use our registry when evaluating which AI extensions to approve. Get your extension assessed before they finalize the allowlist without you.
Contact [email protected] with your Chrome Web Store URL or GitHub repo.
Where to go next
Searchable registry of audited MCP servers, extensions, and AI agents.
Free to browseBrowse Registry11 MCP-specific security rules. Signed cert. Public registry listing.
$249 one-timeGet AuditedFree website compliance scan, paid report, and daily regulatory feed.
Free to startStart Free Scan