Gathering detailed insights and metrics for eslint-plugin-vtex
Gathering detailed insights and metrics for eslint-plugin-vtex
Gathering detailed insights and metrics for eslint-plugin-vtex
Gathering detailed insights and metrics for eslint-plugin-vtex
npm install eslint-plugin-vtex
Module System
Min. Node Version
Typescript Support
Node Version
NPM Version
55 Stars
296 Commits
7 Forks
113 Watching
12 Branches
35 Contributors
Updated on 22 Sept 2024
JavaScript (64.01%)
TypeScript (35.52%)
Shell (0.47%)
Cumulative downloads
Total Downloads
Last day
102.9%
1,804
Compared to previous day
Last week
39.3%
10,596
Compared to previous week
Last month
11.4%
38,508
Compared to previous month
Last year
-7.3%
379,754
Compared to previous year
1
1
Main repository for VTEX's Typescript standards. Issues should be used to start discussions about standards and patterns. PRs are welcome after being rightfully discussed.
docs/
packages/
If you're not using Bash, change
/bin/bash
to your shell's executable path.
1/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/vtex/typescript/master/scripts/bootstrap-typescript.sh)"
Warning: This will override the following configuration files:
.prettierrc
,.eslintrc
andtsconfig.json
.
Nothing is written in stone, so if there's some kind of rule or pattern that you wish to discuss or implement, we encourage an open discussion via this repository issues. The project use labels to keep everything organized and easy-to-find:
discussion
- discussion thread;style
- related to code style, something that there's no wrong or right;practices/patterns
- related to good coding practices that should be standardized and documented;documentation
- a generic documentation issue;todo
- common TODO item, with no explicit SLA.Feel free to use more than one label in an issue, but try keeping them semantic to help developers.
This project uses lerna
with yarn
workspaces, so it's highly recommended to read at least the Lerna documentation.
Running yarn
will automatically install all the dependencies for all packages and link them together when needed.
1yarn
To run a package.json
script on all packages, you can use:
1lerna run {scriptName} 2# will run the scriptName script on all package directories
If you want to only run on some packages, pass a --scope=package-name
to the command above. For more instructions, see the lerna run
documentation.
1lerna run --scope="eslint-*" test 2# run the test script on all packages that match the pattern above
The same can be done for regular shell programs with the lerna exec
command:
1lerna exec "pwd" 2# will print the pwd of all package directories
Note: The quotes are not needed if your command doesn't have a string with spaces.
For every release, there should be at least one new changelog entry for every modified package. This repository follows the keep a changelog format. The chan
CLI can be used to help adding changelog entries:
1chan fixed "Fix that nasty potato bug"
It's also possible to run the command on multiple packages with the lerna exec
command:
1lerna exec "chan fixed 'Fix that nasty potato bug'" 2# note the quotes
Every package has a version
script that will automatically update their changelog with the new version and entries whenever lerna publish
or lerna version
is used.
Relevant commands:
lerna version
- Only update versions without publishing the packages.lerna publish
- Update the version and publish the packages.No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
Found 6/12 approved changesets -- score normalized to 5
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
dependency not pinned by hash detected -- score normalized to 0
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
Reason
security policy file not detected
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Reason
31 existing vulnerabilities detected
Details
Score
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