Top Risks

• Default search engine overridden to search.searchsafe.tech; uninstall and install URL hijacks confirmed — classic monetization shell.
• No developer name listed despite verified-publisher badge; accountability gap.
• Privacy policy admits data collection and third-party sharing but lacks retention disclosure.
• Uninstall/install URL hijacks both present; typical pattern for traffic-redirect extensions.
• Maintenance gap of 13 months (6-12mo band) raises supply-chain staleness concern.

Evidence

• search_provider_override manifest chrome_settings_overrides sets is_default=true to search.searchsafe.tech — forced search hijack.
• uninstall_url_hijack crx uninstall_url_hijack=true; target null but pattern confirmed — webstore signal +3.0.
• install_url_hijack crx install_url_hijack=true; onInstalled opens 3rd-party URL — webstore signal +2.0.
• verified_publisher_featured store Verified publisher + featured badge present; discounts applied but capped due to stale/hijack signals.
• no_developer_name store developer_name is empty string despite verified publisher status.
• privacy_policy_third_party_sharing api Policy fetched; scope_extension=true, data_collection=true, third_party_sharing=true, retention=false.
• js_external_hosts crx Extension contacts github.com and search.searchsafe.tech as external JS hosts.
• maintenance_stale store 13 months since last update; falls in 12-24mo band (+6.0 maintenance score).

Permissions Breakdown

• storage low Persists settings locally; minimal risk on its own.
• chrome_settings_overrides.search_provider (is_default=true) high Silently replaces user's default search engine with searchsafe.tech — core monetization vector.

Pillar Scores

Bookkeeping