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.
@linthtml/linthtml
Advanced tools
The HTML5 linter and validator you need.
LintHTML is a fork of htmllint featuring a built-in CLI and multiple bug fixes and improvements. The migration from htmllint to LintHTML is easy, as all htmllint's rules can be used with LintHTML – just follow this simple guide.
You can install LintHTML either locally or globally. For most cases we recommend the former, which can be achieved this way with npm:
npm install @linthtml/linthtml --save-dev
You should then init a configuration file:
npx linthtml --init
This will generate a file .linthtmlrc
in the current directory.
After that, you can run LintHTML on any file or directory like this:
npx linthtml 'yourfile.html'
npx linthtml 'src/**/*.html'
If you want to read about alternative installation and usage methods, have a look to the installation and usage page in the documentation.
FAQs
LintHTML CLI
We found that @linthtml/linthtml demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers 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.