# Strong brand checking in JavaScript

**URL:** <https://es.discourse.group/t/strong-brand-checking-in-javascript/557>\
**Category:** 💡 Ideas\
**Created:** [November 23, 2020, 12:20pm UTC](https://es.discourse.group/t/strong-brand-checking-in-javascript/557 "2020-11-23T12:20:59Z")\
**Posts on this page:** 1\
**Showing post:** 54

<div class="post-metadata">

**Author:** ![ljharb](https://yyz2.discourse-cdn.com/free1/user_avatar/es.discourse.group/ljharb/32/8_2.png) [@ljharb](https://es.discourse.group/u/ljharb)\
**Post date:** [November 1, 2021, 8:28pm UTC](https://es.discourse.group/t/strong-brand-checking-in-javascript/557/54 "2021-11-01T20:28:47Z")

</div>

You're correct, except that these frameworks already delete any unrecognized globals - but they don't delete unrecognized Function.prototype properties, for example.

In other words, adding this new API as a global is viable; adding it as a prototype method is not. Additionally, being a global means it can be denied in a scope - being a prototype method means it could sneak its way in via any function that crosses a membrane boundary, which would break security invariants.

---

_[View the full topic](https://es.discourse.group/t/strong-brand-checking-in-javascript/557)._