Why permission analysis needs context
A permission name alone says little about risk. The tabs permission can reveal browsing activity, but many tab managers need it. Cookies can expose sessions, but a session manager may require it. The analyzer pairs each permission with a description and a recommendation.
It also reports optional permissions, which can expand access after installation, and host permissions, which define website reach.
Related pages:Chrome permissions checkerManifest V3 permissions list
How the permission category score works
Each known API permission has an impact weight. Required weights are summed and scaled, with a small additional weight for broad-access capabilities. Host permissions are scored separately under website access so the same reach is not counted twice.
The report shows the top weighted permissions and the aggregate. This is a transparent heuristic, not a vendor risk rating.
Related pages:what does all_urls meancookies permission
Using the result
Match each permission to a visible feature. If a capability is unnecessary for the product, prefer an alternative extension with narrower access. Review optional permissions before accepting a runtime prompt.
A permission analyzer informs a decision. It cannot show whether a permission was used or whether data left your browser.