extuno
Extuno vs extension risk scanners
Many browser-extension risk scanners score an extension once from static signals, and some are no longer maintained. Extuno adds a dynamic sandbox, version diffing, and package coverage to the same evidence-led extension scoring, and is actively maintained.
What does a typical extension scanner do?
A browser-extension risk scanner reads an extension from its store and produces a quantified risk score from static signals: the permissions it requests, vulnerable third-party JavaScript libraries it bundles, a weak Content-Security-Policy, and missing store metadata. That is a fast read of what an extension ships, not what it does.
Two limits are common in this category: the analysis is a point-in-time score of static signals, so it does not run the extension or watch how it changes across updates; and some well-known scanners have been discontinued and are no longer maintained, leaving teams without ongoing coverage.
What does Extuno add to that score?
Extuno keeps the idea of an evidence-led risk score and goes further. It reads each version with 1100+ static rules, runs the extension in a network-segmented micro-VM to record the endpoints it contacts and the payloads it sends, then diffs every update against the prior version to catch a clean extension that was poisoned later. It also covers developer packages such as npm, PyPI, and WordPress, and it is actively maintained.
Switching from a static or discontinued scanner
If you used a static extension scanner, or one that is no longer maintained, Extuno covers Chrome and Firefox extension analysis and adds dynamic sandboxing, cross-version diffing, more ecosystems, and a finding format that names the file, the line, why it is dangerous, and the recommended action.