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.
autoprefixer-stylus
Advanced tools
An autoprefixer plugin for stylus.
You can install through npm as such: npm install autoprefixer-stylus
You can include autoprefixer-stylus as a normal stylus plugin. Basic example below:
const stylus = require('stylus')
const autoprefixer = require('autoprefixer-stylus')
stylus(css)
.use(autoprefixer())
.render(function(err, output) {
console.log(output)
})
This plugin also takes any of the options that autoprefixer normally takes. Example with overrideBrowswerslist
below:
stylus(css).use(autoprefixer({ overrideBrowserslist: ['ie 7', 'ie 8'] }))
By default, this plugin will display any warnings. You can disable this with the hideWarnings
option. Example below:
stylus(css)
.use(autoprefixer({ hideWarnings: true });
If you'd like to install globally and run from the command line, you can do it like this:
npm install -g autoprefixer-stylus
stylus -u autoprefixer-stylus -c example.styl
FAQs
autoprefixer for stylus
We found that autoprefixer-stylus 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.