Gathering detailed insights and metrics for @funboxteam/eslint-plugin-no-only-tests
Gathering detailed insights and metrics for @funboxteam/eslint-plugin-no-only-tests
Gathering detailed insights and metrics for @funboxteam/eslint-plugin-no-only-tests
Gathering detailed insights and metrics for @funboxteam/eslint-plugin-no-only-tests
Disallow the use of describe.only() and it.only()
npm install @funboxteam/eslint-plugin-no-only-tests
Typescript
Module System
Node Version
NPM Version
69.9
Supply Chain
78.7
Quality
80.2
Maintenance
100
Vulnerability
100
License
JavaScript (100%)
Total Downloads
191,653
Last Day
65
Last Week
875
Last Month
3,631
Last Year
38,809
MIT License
10 Stars
60 Commits
2 Forks
11 Watchers
2 Branches
8 Contributors
Updated on Dec 30, 2023
Minified
Minified + Gzipped
Latest Version
5.0.0
Package Id
@funboxteam/eslint-plugin-no-only-tests@5.0.0
Unpacked Size
6.11 kB
Size
2.88 kB
File Count
6
NPM Version
9.5.0
Node Version
18.15.0
Published on
May 19, 2023
Cumulative downloads
Total Downloads
Last Day
-77%
65
Compared to previous day
Last Week
-19.7%
875
Compared to previous week
Last Month
14.1%
3,631
Compared to previous month
Last Year
-15.6%
38,809
Compared to previous year
3
Disallow the use of describe.only()
and it.only()
.
When developers fix tests they may make the process easier by filtering tests using method only
on it
& describe
.
However, such filters should not be in the repo when the project is running on CI.
So, we add this rule to our ESLint config to check the existence of only
in the tests files. And we run linter using precommit-hook, which make it possible to prevent committing
when only
does exist in the code.
You'll first need to install ESLint:
$ npm i eslint --save-dev
Next, install the plugin:
$ npm install @funboxteam/eslint-plugin-no-only-tests --save-dev
Add @funboxteam/eslint-plugin-no-only-tests
to the plugins
section of your .eslintrc
configuration file.
You can omit the eslint-plugin-
prefix:
1{ 2 "plugins": [ 3 "@funboxteam/no-only-tests" 4 ] 5}
Then configure the rule under the rules
section.
1{ 2 "rules": { 3 "@funboxteam/no-only-tests/no-only": 2 4 } 5}
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
no dangerous workflow patterns detected
Reason
license file detected
Details
Reason
dependency not pinned by hash detected -- score normalized to 2
Details
Reason
Found 1/7 approved changesets -- score normalized to 1
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Reason
16 existing vulnerabilities detected
Details
Score
Last Scanned on 2025-06-16
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