---
title: "Discussion on \"Review a browser extension before giving it access to your work\" | Hashnode"
description: "Discussion on \"Review a browser extension before giving it access to your work\". Review extension permissions, narrow Chrome site access, and document what you keep. A practical checklist using harmless test data."
url: "https://hashnode.com/posts/review-a-browser-extension-before-giving-it-access-to-your-work/6af1c2cbe36ad5a229e983c3"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Review a browser extension before giving it access to your work](https://onemorelock.hashnode.dev/review-a-browser-extension-before-giving-it-access-to-your-work?utm_source=hashnode&utm_medium=feed)

Review extension permissions, narrow Chrome site access, and document what you keep. A practical checklist using harmless test data.

3d ago · 3 min read · onemorelock.hashnode.dev  
Read the article

-   [#security](https://hashnode.com/tag/security)
-   [#chrome-extension](https://hashnode.com/tag/chrome-extension)

## Written by

[OneMoreLock](https://hashnode.com/@onemorelock)

@onemorelock

  
[View profile](https://hashnode.com/@onemorelock)

## Responses 1

Markdown supported · ⌘↵ to post

[Adam Lewis](https://hashnode.com/@nark3d)

[2d ago](https://hashnode.com/posts/review-a-browser-extension-before-giving-it-access-to-your-work/6af1c2cbe36ad5a229e983c3/comment/6af2e7a3e7e8c4a507c854f5)

Read-only site access is a weaker control than the panel makes it look, because the extension still runs its content script and can read what's on the page while it's there; the permission just decides whether it gets to keep talking to that tab afterwards. And the setting doesn't cover VPN and proxy access at all, so someone can tighten it, see the workflow pass and conclude the extension is boxed in when it isn't. Narrower is worth doing, but it's worth being clear-eyed about what it buys.