
Research
/Security News
Critical Vulnerability in NestJS Devtools: Localhost RCE via Sandbox Escape
A flawed sandbox in @nestjs/devtools-integration lets attackers run code on your machine via CSRF, leading to full Remote Code Execution (RCE).
checkstyle-filter-by-name
Advanced tools
Library for filtering rules from a checkstyle file
This library can be installed from the NPM package registry. Depending on your use case it might be better to install this package globally (if you want to run these commands from your continuous integration server for example)
Using NPM:
npm install checkstyle-filter-by-name
or Yarn
yarn add checkstyle-filter-by-name
From the command line you can run this command
./node_modules/.bin/checkstyle-filter-by-name -i [filename] -o [filename] -e [exclude regex]"
There are three command line arguments:
short arg | long arg | effect |
---|---|---|
-i | --input | the file to read from |
-o | --output | the file to write to, option, if not included will write to input file |
-e | --exclude | the javascript regex to determine which checkstyle entries get excluded |
Passing along the -e or --exclude flag will exclude entries within the checkstyle file that match the given regular expression.
A check is performed using standard javascript regexp: RegExp(..passes argument..).test(..checkstyle entry name..)
.
If this function returns true the file is skipped.
Given a file with these rules:
<?xml version="1.0" encoding="utf-8"?>
<checkstyle version="4.3">
<file name="node_modules/example/example.d.ts">
<error line="1" column="1" severity="error" message="Example" source="TS2344" />
</file>
<file name="example/example.d.ts">
<error line="1" column="1" severity="error" message="Example" source="TS2344" />
</file>
</checkstyle>
Running this command:
checkstyle-filter-by-name -i typescript-error.xml -e "node_modules\\/"
Will result in a file with these rules:
<?xml version="1.0" encoding="utf-8"?>
<checkstyle version="4.3">
<file name="example/example.d.ts">
<error line="1" column="1" severity="error" message="Example" source="TS2344" />
</file>
</checkstyle>
This project adheres to Semantic Versioning.
Contributions to this project are more than welcome.
This project is released under the MIT license.
This package is Treeware. If you use it in production, then we'd appreciate it if you buy the world a tree to thank us for our work. By contributing to the Treeware forest you'll be creating employment for local families and restoring wildlife habitats.
Made with love, coffee and fun by the Moxio team from Delft, The Netherlands. Interested in joining our awesome team? Check out our vacancies (in Dutch).
FAQs
Filtering a checkstyle file
The npm package checkstyle-filter-by-name receives a total of 1 weekly downloads. As such, checkstyle-filter-by-name popularity was classified as not popular.
We found that checkstyle-filter-by-name demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
/Security News
A flawed sandbox in @nestjs/devtools-integration lets attackers run code on your machine via CSRF, leading to full Remote Code Execution (RCE).
Product
Customize license detection with Socket’s new license overlays: gain control, reduce noise, and handle edge cases with precision.
Product
Socket now supports Rust and Cargo, offering package search for all users and experimental SBOM generation for enterprise projects.