Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
mojito-cli-jslint
Advanced tools
mojito-jslint ========== <!-- [![Build Status](https://travis-ci.org/yahoo/{{name}}.png)](https://travis-ci.org/yahoo/{{name}}) -->
This package provides the jslint
command for the mojito-cli
. Install it with npm install -g mojito-cli
.
To check for jslint errors in your application:
mojito jslint app
To run JSLint on a specific mojit:
mojito jslint mojit <mojit-name-or-path>
--print
-p
--exclude
-e
--directory
-d
http://developer.yahoo.com/forum/Yahoo-Mojito
BSD licensed (see LICENSE.txt). To contribute to the Mojito project, please see Contributing.
The Mojito project is a meritocratic, consensus-based community project, which allows anyone to contribute and gain additional responsibilities.
FAQs
Provide the jslint command for mojito-cli
The npm package mojito-cli-jslint receives a total of 7 weekly downloads. As such, mojito-cli-jslint popularity was classified as not popular.
We found that mojito-cli-jslint 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.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.