Gathering detailed insights and metrics for confusing-browser-globals
Gathering detailed insights and metrics for confusing-browser-globals
Gathering detailed insights and metrics for confusing-browser-globals
Gathering detailed insights and metrics for confusing-browser-globals
@types/confusing-browser-globals
TypeScript definitions for confusing-browser-globals
confusing-browser-globals-fresh
A list of browser globals that are often used by mistake instead of local variables
@duplotech/confusing-browser-globals
A list of browser globals that are often used by mistake instead of local variables
augle-confusing-browser-globals
A list of browser globals that are often used by mistake instead of local variables
Set up a modern web app by running one command.
npm install confusing-browser-globals
Typescript
Module System
Node Version
NPM Version
JavaScript (98.35%)
Shell (1.21%)
CSS (0.15%)
HTML (0.12%)
AppleScript (0.09%)
TypeScript (0.07%)
SCSS (0.02%)
Sass (0.01%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
MIT License
103,365 Stars
2,819 Commits
27,032 Forks
1,900 Watchers
28 Branches
960 Contributors
Updated on Jul 16, 2025
Latest Version
1.0.11
Package Id
confusing-browser-globals@1.0.11
Unpacked Size
3.78 kB
Size
2.03 kB
File Count
4
NPM Version
lerna/4.0.0/node@v16.13.0+arm64 (darwin)
Node Version
16.13.0
Published on
Dec 14, 2021
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
1
A curated list of browser globals that commonly cause confusion and are not recommended to use without an explicit window.
qualifier.
Some global variables in browser are likely to be used by people without the intent of using them as globals, such as status
, name
, event
, etc.
For example:
1handleClick() { // missing `event` argument
2 this.setState({
3 text: event.target.value // uses the `event` global: oops!
4 });
5}
This package exports a list of globals that are often used by mistake. You can feed this list to a static analysis tool like ESLint to prevent their usage without an explicit window.
qualifier.
1npm install --save confusing-browser-globals
If you use Create React App, you don't need to configure anything, as this rule is already included in the default eslint-config-react-app
preset.
If you maintain your own ESLint configuration, you can do this:
1const restrictedGlobals = require('confusing-browser-globals'); 2 3module.exports = { 4 rules: { 5 'no-restricted-globals': ['error'].concat(restrictedGlobals), 6 }, 7};
MIT
No vulnerabilities found.
Reason
security policy file detected
Details
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
Found 11/15 approved changesets -- score normalized to 7
Reason
dependency not pinned by hash detected -- score normalized to 2
Details
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Reason
93 existing vulnerabilities detected
Details
Score
Last Scanned on 2025-07-07
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More