pinst VS audit-ci

Compare pinst vs audit-ci and see what are their differences.

pinst

🍺 dev only postinstall hooks (package.json) (by typicode)

audit-ci

Audit NPM, Yarn, and PNPM dependencies in continuous integration environments, preventing integration if vulnerabilities are found at or above a configurable threshold while ignoring allowlisted advisories (by IBM)
Our great sponsors
  • SurveyJS - Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
pinst audit-ci
1 1
256 254
- 0.4%
0.0 4.1
about 1 year ago 26 days ago
JavaScript TypeScript
MIT License Apache License 2.0
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.

pinst

Posts with mentions or reviews of pinst. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-02-08.

audit-ci

Posts with mentions or reviews of audit-ci. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-07-07.
  • NPM Audit: Broken by Design
    7 projects | news.ycombinator.com | 7 Jul 2021
    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?

When comparing pinst and audit-ci you can also consider the following projects:

husky - Git hooks made easy 🐶 woof!

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

simple-git-hooks - A simple git hooks manager for small projects

is-number - JavaScript/Node.js utility. Returns `true` if the value is a number or string number. Useful for checking regex match results, user input, parsed strings, etc.

lefthook - Fast and powerful Git hooks manager for any type of projects.

salus - We would like to request that all contributors please clone a *fresh copy* of this repository since the September 21st maintenance.

ci - Run npm ci using the appropriate Node package manager (npm, yarn, pnpm)

pwndoc - Pentest Report Generator

react-universal-hooks - :tada: React Universal Hooks : just use****** everywhere (Functional or Class Component). Support React DevTools!

safe-npm - safe npm time travel installs

swpm - Switch Package Manager - Say goodbye to Package Manager confusion

pkg-vuln-collab-space - Project for work on improved Package Vulnerability Management & Reporting