lockfile-lint
awesome-lint
Our great sponsors
| lockfile-lint | awesome-lint | |
|---|---|---|
| 5 | 2 | |
| 767 | 591 | |
| - | - | |
| 7.6 | 7.2 | |
| 2 months ago | 4 months ago | |
| JavaScript | JavaScript | |
| Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
lockfile-lint
-
How to Effortlessly Improve a Legacy Codebase Using Robots
Run static analysis e.g. lint with lockfile-lint, Stylelint, ESLint, check for unimported files using unimported, and identify potential security vulnerabilities
-
The rising trend of malicious packages in open source ecosystems | Snyk
I built a lockfile-lint (https://github.com/lirantal/lockfile-lint) that helps with ensuring that some of these trust policies are enforced.
-
How to respond to growing supply chain security risks?
And it is happening right now. Github is opening the GitHub Advisory Database to community submissions. Awesome community NodeSecure builds cool things like scanner and js-x-ray. There are also lockfile-lint, LavaMoat, Jfrog-npm-tools (and I am sure there is more).
-
Injecting backdoors to NPM packages
An additional approach may be to use lockfile-lint, but you shouldn't just rely on this script entirely because there are other ecosystems than npm, and they may have similar issues.
-
JavaScript Security 101
Use lockfile lint to check changes in the package-lock.json which is typically not reviewed
awesome-lint
-
Potherca's Weekly Github Stars - 2020 Week 25
What I mean by versionless, is that this Action allows consumers to specify the version of the awesome-lint package they desire.
-
Prefer the English Style of Quotation Mark Punctuation over the American
I tried to implement some linting rules for quotation mark and punctuation once. Took me way too much time and effort. It's mostly trial and error but good enough I guess to highlight the most blatant abuses.
Anyway, here is the code: https://github.com/sindresorhus/awesome-lint/pull/101/files
What are some alternatives?
node-safe - 🤠 Make using Node.js safe again with Deno-like permissions
nano-staged - Tiny tool to run commands for modified, staged, and committed files in a GIT repository.
folderslint - 📁 Directory structure linter for Front-End projects
data-transfer-project - The Data Transfer Project makes it easy for people to transfer their data between online service providers. We are establishing a common framework, including data models and protocols, to enable direct transfer of data both into and out of participating online service providers.
np - A better `npm publish`
starred - creating your own Awesome List by GitHub stars!
tbv - Package verification for npm
github-action-awesome-lint - GitHub Action for awesome-lint where you specify the package version!
unimported - Find and fix dangling files and unused dependencies in your JavaScript projects.
stylelint - A mighty CSS linter that helps you avoid errors and enforce conventions.
awesome-nodejs-security - Awesome Node.js Security resources
data-transfer-projectCODE_OF_CONDUCT.md