Ext Ops Panel
Open dashboard
Permissions and history

Is Atlassian Forge DevTools safe to install?

Atlassian Forge DevTools asks for 1 browser permission and declares no blanket site access. We do not audit code and we do not judge intent; what we can show is what the listing declares and whether that has changed while we have been watching.

Atlassian Forge DevTools

Chrome extension by João Brilhante · Productivity · Developer

Open in the Chrome Web Store
What the developer says, and 4 screenshots

Loading from the Chrome Web Store. Open the listing if it does not appear.

At a glance

Facts, not a score: an ad blocker needs every page and a theme needs nothing, so one number would be wrong about both. Each fact links to its detail.

Site access
No site access
Data collection
Declares it collects none
Publisher
No store badges
Audience
69 users · 5.0/5

What data it declares

The developer declares that it does not collect or use your data.

The developer also certifies that your data is not sold to third parties outside approved uses, not used for purposes unrelated to the extension's core function, and not used to decide creditworthiness or lending.

The listing does not link to a privacy policy.

This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.

What Chrome asks you to allow

From the permissions it declares, Chrome shows no permission warning when you add it.

Derived from the manifest by Chrome's documented rules; the dialog's exact wording depends on your Chrome version and language. Chrome asks again if an update requests more.

What it can reach

No site access is declared in the manifest, so it cannot read the pages you open on its own.

Routine for an extension

How usual this is for its category

In Productivity · Developer, 30% of extensions ask for access to every site. This one: No site access.

The typical extension there declares 3 browser permissions; this one declares 1 browser permission.

Counted over the live extensions of the same category after our latest full pass of the store. A share is context, not a verdict: what is normal depends on what the extension is for.

Who uses it and how it is kept up

69 users

Users
+15 since 01.09
54-71 · 33 readings
2026-09-07: released 1.2.52026-09-08: released 1.3.02026-09-13: released 1.4.0
  1. 2026-09-0154
  2. 2026-09-0255
  3. 2026-09-0454
  4. 2026-09-0654
  5. 2026-09-0755released 1.2.5
  6. 2026-09-0956
  7. 2026-09-1054
  8. 2026-09-1355released 1.4.0
  9. 2026-09-1756
  10. 2026-09-2154
  11. 2026-09-2558
  12. 2026-09-2757
  13. 2026-09-2856
  14. 2026-10-0460
  15. 2026-10-0866
  16. 2026-10-0967
  17. 2026-10-1062
  18. 2026-10-1363
  19. 2026-10-1665
  20. 2026-10-1865
  21. 2026-10-2166
  22. 2026-10-2265
  23. 2026-10-2367
  24. 2026-10-2466
  25. 2026-10-2767
  26. 2026-10-2968
  27. 2026-11-0169
  28. 2026-11-0368
  29. 2026-11-0571
  30. 2026-11-0769
  31. 2026-11-0867
  32. 2026-11-1069
  33. 2026-11-1169

What the store shows

The store shows none of its badges on this listing. Most listings carry none.

Has it asked for more over time?

This is the question a permission list on its own cannot answer. An extension that shipped narrow and widened later is a different proposition from one that always asked for the same thing.

The permissions this extension requests have not changed since we started watching it.

Versions we have seen

  1. Version 1.4.0
  2. Version 1.3.0
  3. Version 1.2.5

Who publishes it

João Brilhante. This listing has been in the store since 2026-03-30 and was last updated on 2026-09-12.

Similar extensions that ask for less

Listings close to this one in what they say they do, which declare less reach. Less reach is not a verdict on either: compare what each needs for the job.

  1. Atlassian Forge Dev Tools No permissions at all · No permissions declared 78 users

How to check or remove it in Chrome

  1. Type chrome://extensions in the address bar and find the extension in the list.
  2. Open its details. The site access setting shows where it can run; set it to run only on click and it reaches a page only after you press its icon.
  3. To uninstall it, choose Remove on the same page.

Questions people ask

What can Atlassian Forge DevTools access?
No site access is declared in the manifest, so it cannot read the pages you open on its own. It declares 1 browser permission.
What data does Atlassian Forge DevTools collect?
The developer declares that it does not collect or use your data. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has Atlassian Forge DevTools asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does Atlassian Forge DevTools publish a privacy policy?
No, the store listing does not link to a privacy policy.

We read the public store listing up to 2 times a day and keep what it declared. We do not install the extension, do not audit its code, do not judge its intent and publish no contact details for its developer. Last read on 2026-11-11.

Back to Atlassian Forge DevTools · Alternatives to Atlassian Forge DevTools

Where the data comes from: how the catalog is built