Gathering detailed insights and metrics for eslint-plugin-cypress-test-best-practices
Gathering detailed insights and metrics for eslint-plugin-cypress-test-best-practices
Installations
npm install eslint-plugin-cypress-test-best-practicesReleases
13
Try Catch - At Least 1 Assertion
0.1.5
Published on 13 Jan 2021
Tested - cruk_commerce
0.1.4
Published on 11 Jan 2021
Fix Template Literal - Part 2
0.1.3-fix
Published on 11 Jan 2021
Template Literal - Fixed
0.1.3-fixed
Published on 11 Jan 2021
Template Literal
0.1.3
Published on 11 Jan 2021
more tests
0.1.2
Published on 23 Dec 2020
Developer
lewis-prescott-cruk
Developer Guide
BETA
Module System
CommonJS
Min. Node Version
>=0.10.0
Typescript Support
No
Node Version
10.23.0
NPM Version
6.14.8
Statistics
19 Commits
2 Watching
1 Branches
1 Contributors
Updated on 13 Jan 2021
Languages
JavaScript (100%)
Total Downloads
Cumulative downloads
Total Downloads
80,038
Last day
-36.6%
241
Compared to previous day
Last week
-16.2%
1,279
Compared to previous week
Last month
20.8%
6,242
Compared to previous month
Last year
165.9%
56,507
Compared to previous year
Daily Downloads
Weekly Downloads
Monthly Downloads
Yearly Downloads
Dependencies
1
Peer Dependencies
2
Versions
eslint-plugin-cypress-test-best-practices
best practices for cypress tests. From my experience at Cancer Research UK.
Installation
You'll first need to install ESLint:
$ npm i eslint --save-dev
Next, install eslint-plugin-cypress-test-best-practices:
$ npm install eslint-plugin-cypress-test-best-practices --save-dev
Peer dependencies
$ npm install eslint-plugin-cypress --save-dev
$ npm install eslint-plugin-chai-friendly --save-dev
Usage
Add cypress-test-best-practices to the plugins section of your .eslintrc configuration file. You can omit the eslint-plugin- prefix:
1{ 2 "plugins": [ 3 "cypress-test-best-practices" 4 ] 5}
Then configure the rules you want to use under the rules section.
1{ 2 "rules": { 3 "cypress-test-best-practices/at-least-one-assertion": 2 4 } 5}
Use the recommended configuration and you can forego configuring rules individually. See below for which rules are included.
1{ 2 "extends": [ 3 "plugin:cypress-test-best-practices/recommended" 4 ] 5}
Supported Rules
- See
docsfolder
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/publish.yml:9: update your workflow using https://app.stepsecurity.io/secureworkflow/lewis-prescott-cruk/eslint-plugin-cypress-test-best-practices/publish.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/publish.yml:10: update your workflow using https://app.stepsecurity.io/secureworkflow/lewis-prescott-cruk/eslint-plugin-cypress-test-best-practices/publish.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/publish.yml:15: update your workflow using https://app.stepsecurity.io/secureworkflow/lewis-prescott-cruk/eslint-plugin-cypress-test-best-practices/publish.yml/main?enable=pin
- Warn: npmCommand not pinned by hash: .github/workflows/publish.yml:14
- Info: 0 out of 2 GitHub-owned GitHubAction dependencies pinned
- Info: 0 out of 1 third-party GitHubAction dependencies pinned
- Info: 0 out of 1 npmCommand dependencies pinned
Reason
Found 0/19 approved changesets -- score normalized to 0
Reason
detected GitHub workflow tokens with excessive permissions
Details
- Warn: no topLevel permission defined: .github/workflows/publish.yml:1
- Info: no jobLevel write permissions found
Reason
no SAST tool detected
Details
- Warn: no pull requests merged into dev branch
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
license file not detected
Details
- Warn: project does not have a license file
Reason
branch protection not enabled on development/release branches
Details
- Warn: branch protection not enabled for branch 'main'
Reason
12 existing vulnerabilities detected
Details
- Warn: Project is vulnerable to: GHSA-93q8-gq69-wqmw
- Warn: Project is vulnerable to: GHSA-grv7-fg5c-xmjg
- Warn: Project is vulnerable to: GHSA-3xgq-45jj-v275
- Warn: Project is vulnerable to: GHSA-gxpj-cx7g-858c
- Warn: Project is vulnerable to: GHSA-2j2x-2gpw-g8fm
- Warn: Project is vulnerable to: GHSA-ww39-953v-wcq6
- Warn: Project is vulnerable to: GHSA-29mw-wpgm-hmr9
- Warn: Project is vulnerable to: GHSA-35jh-r3h4-6jhm
- Warn: Project is vulnerable to: GHSA-f8q6-p94x-37v3
- Warn: Project is vulnerable to: GHSA-xvch-5gv4-984h
- Warn: Project is vulnerable to: GHSA-c2qf-rxjj-qqgw
- Warn: Project is vulnerable to: GHSA-j8xg-fqg3-53r7
Score
2.2
/10
Last Scanned on 2024-11-18
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