Salesforce developers and admins lack a fast way to search across Apex classes, triggers, Visualforce pages, Lightning components, and other code components within the Salesforce setup interface. The native Salesforce setup UI requires navigating through multiple pages to find and access code components.

1. User navigates to Salesforce Setup home page (Classic or Lightning). 2. The extension injects a tabbed developer utilities panel into the setup page. 3. On first use, user clicks 'Authorize' to initiate Salesforce OAuth2 flow - selecting org type (Production/Sandbox/Developer). 4. User is redirected to Salesforce login, grants OAuth consent, and is redirected back via callback.html. 5. The Firebase backend exchanges the auth code for tokens (access_token, refresh_token). 6. Tokens are stored in localStorage for subsequent API calls. 7. User can now search code components (using Salesforce Tooling API), run static analysis, extract code coverage, edit LWC components, explore GraphQL, and look up record details - all without leaving the setup page.

Target users: Salesforce developers / Salesforce administrators / Salesforce technical consultants

The build/static/js/main.9a2068da.js is a minified React bundle (482KB) that is difficult to fully analyze, though it appears to be related to a secondary LWC editor or GraphQL explorer feature
Could not fully verify whether the Firebase Cloud Functions backend imposes any usage limits or has paid tiers
The monaco-editor directory is very large (1000+ files) and contains third-party VS Code editor code, not extension-specific logic

Monetization

No paid features detected

No evidence of paid features, premium tiers, subscriptions, or payment mechanisms within the extension. Searches for 'premium', 'pricing', 'stripe', 'payment', and 'billing' returned no relevant matches in the extension's own code. The 'subscription' matches are all from monaco-editor internals (event subscriptions, not billing). The 'upgrade' matches are about browser/IndexedDB upgrades. The 'checkout' match in contentScript_l.js is a Twitter sharing link ('Checkout the updated version...'). The 'license' matches are all standard open-source library license declarations (MIT, React, etc.). All features (code search, static analysis, code coverage, LWC editor, GraphQL explorer) appear to be freely available without any gating.

Confidence: 90
Payment platform: --
Source: AI / High
Login required: Needs review
Reason: The extension requires Salesforce OAuth2 authorization to function. Users must authorize the extension to access their Salesforce org data via OAuth flow. login.html presents org type selection (Sandbox/Production/Developer), login.js initiates Salesforce OAuth2 with a Connected App client ID, callback.js exchanges the auth code via a Firebase backend (us-central1-sf-advanced-code-searcher.cloudfunctions.net/authorizeSalesforce), and factory.js stores tokens (accessToken, refreshToken, instanceURL). Multiple directives check authenticationStatus and block features when 'Auth Needed'. The contentScript_l.js shows 'Click here to authorize (one time)' button and a 'Re-Authenticate' link. This is a one-time Salesforce OAuth grant, not a recurring login to the extension's own account system.

Permission risk

Medium-risk permissions

This estimate uses declared permissions and host permissions to assess access scope and sensitivity.

未命中敏感权限或广域站点访问规则

Publisher

Sameer N Miraj

Independent publisher

Email: [email protected]
Phone: --
Address: --

Public contact fields are shown above. Developer portfolio pages are available on paid accounts.

View developer portfolio

Permissions

Host access