
Research
Malicious Go “crypto” Module Steals Passwords and Deploys Rekoobe Backdoor
An impersonated golang.org/x/crypto clone exfiltrates passwords, executes a remote shell stager, and delivers a Rekoobe backdoor on Linux.
pretty-standard
Advanced tools
JavaScript standard lint rules with prettier style and formatting.
Write up coming soon.. tl;dr standard is an opinionated linter, prettier is an opinionated formatter. Both tools are great and very comprehensive. All of the eslint, standard and prettier have been engineered impressively well and are very pluggable. This package just puts them all together in a way that works out of the box so you don't have to.
npm install pretty-standard
All non style related standard rules which leaves code style to prettier. More specifically this package combines the following:
--fix flagInstall globally or locally with:
npm install pretty-standard
npm install pretty-standard -g
Then run in your project, the typical standard defaults and ignores apply:
$ pretty-standard
pretty-standard: Standard eslint rules with prettier formatting
pages/index.js:9:3: 'useState' is not defined.
Or pass --fix to format your code using prettier, which will also log the linting errors that can not be fixed by prettier:
$ pretty-standard --fix
Coming soon to Sublime, VSCode and Atom!
Add it to package.json.
{
"name": "my-cool-package",
"devDependencies": {
"pretty-standard": "*"
},
"scripts": {
"test": "pretty-standard && ava",
"format": "pretty-standard --fix"
}
}
To use a custom parser, install it from npm (example: npm install babel-eslint) and add it to your package.json, this is sometimes necessary when using futuristic JS features:
{
"pretty-standard": {
"parser": "babel-eslint"
}
}
Install Syntastic and add these lines to .vimrc:
let g:syntastic_javascript_checkers=['standard']
let g:syntastic_javascript_standard_exec = 'pretty-standard'
For automatic formatting on save, add these two lines to .vimrc:
autocmd bufwritepost *.js silent !pretty-standard % --fix
set autoread
Just like in standard, The paths node_modules/**, *.min.js, bundle.js, coverage/**, hidden files/folders
(beginning with .), and all patterns in a project's root .gitignore file are
automatically excluded when looking for .js files to check.
Sometimes you need to ignore additional folders or specific minfied files. To do that, add
a pretty-standard.ignore property to package.json:
"pretty-standard": {
"ignore": [
"**/out/",
"/lib/select2/",
"/lib/ckeditor/",
"tmp.js"
]
}
snazzyIf you want prettier output, install snazzy package and pipe pretty-standard to it:
$ pretty-standard --verbose | snazzy
See standard/standard for more information.
FAQs
Please use healthier instead
The npm package pretty-standard receives a total of 1 weekly downloads. As such, pretty-standard popularity was classified as not popular.
We found that pretty-standard 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
An impersonated golang.org/x/crypto clone exfiltrates passwords, executes a remote shell stager, and delivers a Rekoobe backdoor on Linux.

Security News
npm rolls out a package release cooldown and scalable trusted publishing updates as ecosystem adoption of install safeguards grows.

Security News
AI agents are writing more code than ever, and that's creating new supply chain risks. Feross joins the Risky Business Podcast to break down what that means for open source security.