Home
Docs
GitHub
Pricing
Blog
Log In

Run Sandworm Audit for your App

Get started
Hold on, we're currently generating a fresh version of this report
Generated on Apr 11, 2024 via pnpm
Package summary
Share
0
issues
4
licenses
47
MIT
4
ISC
1
Apache-2.0
1
(MIT OR CC0-1.0)
Package created
15 Jan 2016
Version published
21 Aug 2023
Maintainers
1
Total deps
53
Direct deps
10
License
MIT

Issues

0
This package has no issues

Licenses

MIT License

Permissive
OSI Approved
This is a human-readable summary of (and not a substitute for) the license. Disclaimer.
Can
commercial-use
modify
distribute
sublicense
private-use
Cannot
hold-liable
Must
include-copyright
include-license
47 Packages, Including:
ansi-escapes@5.0.0
ansi-regex@6.0.1
ansi-styles@6.2.1
braces@3.0.2
chalk@5.3.0
cli-cursor@4.0.0
cli-truncate@3.1.0
colorette@2.0.20
commander@11.0.0
cross-spawn@7.0.3
debug@4.3.4
eastasianwidth@0.2.0
emoji-regex@9.2.2
eventemitter3@5.0.1
execa@7.2.0
fill-range@7.0.1
get-stream@6.0.1
is-fullwidth-code-point@4.0.0
is-number@7.0.0
is-stream@3.0.0
lilconfig@2.1.0
lint-staged@14.0.1
listr2@6.6.1
log-update@5.0.1
merge-stream@2.0.0
micromatch@4.0.5
mimic-fn@2.1.0
mimic-fn@4.0.0
ms@2.1.2
npm-run-path@5.3.0
onetime@5.1.2
onetime@6.0.0
path-key@3.1.1
path-key@4.0.0
picomatch@2.3.1
pidtree@0.6.0
restore-cursor@4.0.0
rfdc@1.3.1
shebang-command@2.0.0
shebang-regex@3.0.0
slice-ansi@5.0.0
string-argv@0.3.2
string-width@5.1.2
strip-ansi@7.1.0
strip-final-newline@3.0.0
to-regex-range@5.0.1
wrap-ansi@8.1.0

ISC License

Permissive
OSI Approved
This is a human-readable summary of (and not a substitute for) the license. Disclaimer.
Can
commercial-use
modify
distribute
Cannot
hold-liable
Must
include-copyright
include-license
4 Packages, Including:
isexe@2.0.0
signal-exit@3.0.7
which@2.0.2
yaml@2.3.1

Apache License 2.0

Permissive
OSI Approved
This is a human-readable summary of (and not a substitute for) the license. Disclaimer.
Can
commercial-use
modify
distribute
sublicense
private-use
use-patent-claims
place-warranty
Cannot
hold-liable
use-trademark
Must
include-copyright
include-license
state-changes
include-notice
1 Packages, Including:
human-signals@4.3.1

(MIT OR CC0-1.0)

Public Domain
1 Packages, Including:
type-fest@1.4.0
Disclaimer

This deed highlights only some of the key features and terms of the actual license. It is not a license and has no legal value. You should carefully review all of the terms and conditions of the actual license before using the licensed material.

Sandworm is not a law firm and does not provide legal services. Distributing, displaying, or linking to this deed or the license that it summarizes does not create a lawyer-client or any other relationship.

Direct Dependencies

10
All Dependencies CSV
β“˜ This is a list of lint-staged 's direct dependencies. Data on all dependencies, including transitive ones, is available via CSV download.
NameVersionSizeLicenseTypeVulnerabilities
chalk5.3.013.08 kBMIT
prod
commander11.0.044.33 kBMIT
prod
debug4.3.412.94 kBMIT
prod
execa7.2.018.85 kBMIT
prod
lilconfig2.1.04.4 kBMIT
prod
listr26.6.157.6 kBMIT
prod
micromatch4.0.514.09 kBMIT
prod
pidtree0.6.07.11 kBMIT
prod
string-argv0.3.22.89 kBMIT
prod
yaml2.3.1105.09 kBISC
prod

Visualizations

Frequently Asked Questions

What does lint-staged do?

Lint-staged is a JavaScript module designed to enhance code quality by running linters on staged Git files. With lint-staged, you can ensure that your codebase remains clean and maintainable by preventing unwanted or non-standard code from making it into your repository.

How do you use lint-staged?

To start using lint-staged, first install the package using the following command in your terminal:

npm install --save-dev lint-staged

Once installed, you need to setup a pre-commit hook to run lint-staged. A popular choice for this setup is Husky. Install some linters, like ESLint or Prettier, then configure lint-staged to run those linters and other tasks on specific file types.

Here's an example setup in your package.json:

{
  "lint-staged": {
    "*.js": "eslint",
    "*.{json,md}": "prettier --write"
  }
}

After this setup, when you try to commit your changes, lint-staged will run the assigned tasks on the staged files. If all tasks pass, the changes are successfully committed. If any task fails, the commit is aborted.

Where are the lint-staged docs?

The best place to find the lint-staged documentation is on the project's GitHub repository at https://github.com/okonet/lint-staged. The readme file on the repository's main page contains detailed instructions and examples for different use cases. This document is the go-to reference for understanding the initial setup, configuration options and supported commands, usage examples, and resolving common issues.