is-number
audit-ci
Our great sponsors
| is-number | audit-ci | |
|---|---|---|
| 5 | 1 | |
| 245 | 254 | |
| - | 0.4% | |
| 0.0 | 4.4 | |
| over 1 year ago | 16 days ago | |
| JavaScript | TypeScript | |
| MIT License | Apache License 2.0 |
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.
is-number
-
The honest truth about this subreddit
is-number https://github.com/jonschlinkert/is-number *
-
NPM – is-even, 160k weekly downloads
Looks like the author of these packages agrees. While the is-even and is-odd packages are under the i-voted-for-trump user with the description "This is a joke", the is-number package [1] is still kept under the main profile of the author, the repository is still active on GitHub and there are active issues.
-
BREAKING!! NPM package ‘ua-parser-js’ with more than 7M weekly download is compromised
Not[1] one[2] package[3] has more than 15 lines of actual code inside.
-
NPM Audit: Broken by Design
> not what the code in this package does
Here's `is-number` (https://github.com/jonschlinkert/is-number/blob/master/index...):
module.exports = function(num) { -
every function gotta be a package
Which also depends upon is-number
audit-ci
-
NPM Audit: Broken by Design
For those hoping to run npm audit in your CI/CD pipeline, I recommend this tool from IBM: https://github.com/IBM/audit-ci
In highly regulated industries, shipping code flagged as having a vuln without a manual approval could be a liability.
This wrapper around npm takes an allowlist argument, and our procedure is for an engineer to review the failing build, determine if the vulnerability (ugh, usually regex ddos or prototype pollution) is present in code that runs only at build time with trusted inputs, only on the client which is by definition untrusted, or in our webserver which takes in untrusted input.
As long as it's either of the first two, we document it in a commit and comment and redeploy. It's annoying, but it's far better than npm audit forcing a fix.
What are some alternatives?
romanice-dart - A Dart library for converting to/from Roman numerals.
enquirer - Stylish, intuitive and user-friendly prompts, for Node.js. Used by eslint, webpack, yarn, pm2, pnpm, RedwoodJS, FactorJS, salesforce, Cypress, Google Lighthouse, Generate, tencent cloudbase, lint-staged, gluegun, hygen, hardhat, AWS Amplify, GitHub Actions Toolkit, @airbnb/nimbus, and many others! Please follow Enquirer's author: https://github.com/jonschlinkert
salus - We would like to request that all contributors please clone a *fresh copy* of this repository since the September 21st maintenance.
npm-force-resolutions - Force npm to install a specific transitive dependency version
pinst - 🍺 dev only postinstall hooks (package.json)
micromatch - Highly optimized wildcard and glob matching library. Faster, drop-in replacement to minimatch and multimatch. Used by square, webpack, babel core, yarn, jest, ract-native, taro, bulma, browser-sync, stylelint, nyc, ava, and many others! Follow micromatch's author: https://github.com/jonschlinkert
pwndoc - Pentest Report Generator
is-odd - I created this in 2014, the year I learned how to program. All of the downloads are from an old version of https://github.com/micromatch/micromatch. I've done a few other things since: https://github.com/jonschlinkert.
safe-npm - safe npm time travel installs
pkg-vuln-collab-space - Project for work on improved Package Vulnerability Management & Reporting