SoldScope: eBay Sold History, Sold Listings Sort, Sell-Through & Comps extension
Security at a glance
Describes the Chrome listing; other stores are scanned separately and can score differently. Automated estimate from our latest scan (malware, permissions, obfuscation) — not a security audit. Higher safety score is better.
See the full security reportChrome listing ID: gncdkoamdfpminkbbjchmmcaikjillld
Permissions (1)
- Store local data
Related extensions
eBay Sold ListingsShopping
CardComps — Card Values for eBayShopping
eBay Sold History - Item Purchase History & Seller ResearchShopping
SoldScope: eBay Sold History, Sold Listings Sort, Sell-Through & CompsShopping
CompSniper: eBay Sold Listings, Price Checker & Card CompsShopping
SlabStats - Sports Card Sold CompsShopping
Frequently asked questions
Is SoldScope: eBay Sold History, Sold Listings Sort, Sell-Through & Comps safe to use?
Our latest automated scan rates the Chrome listing of SoldScope: eBay Sold History, Sold Listings Sort, Sell-Through & Comps at 97/100 (low risk) — malware, permission and obfuscation checks combined. The full report lists every finding behind the number. This is an automated estimate, not a guarantee of safety.
What permissions does SoldScope: eBay Sold History, Sold Listings Sort, Sell-Through & Comps require?
SoldScope: eBay Sold History, Sold Listings Sort, Sell-Through & Comps requests 1 permission. The most significant: Store local data. See the full breakdown in the security report.
Who develops SoldScope: eBay Sold History, Sold Listings Sort, Sell-Through & Comps?
SoldScope: eBay Sold History, Sold Listings Sort, Sell-Through & Comps is published by SoldScope. Impersonators copy popular extension names, so always verify the developer line and listing id on the store page before installing.
What this assessment covers
- Store listing
- Chrome
- Checked version
- 0.4.4
- Current listed version
- 0.4.4
- Scan date (UTC)
- Assessment status
- Completed
Recorded findings: 0 critical and 0 high severity. Read the finding details before interpreting the score; automated flags are not proof of malicious behaviour.
Automated analysis looks for suspicious code, permissions and other risk signals. It does not observe every runtime behaviour or independently audit the publisher’s servers. A low-risk result is not a guarantee of safety. How our checks work.