npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

gitlab-npm-audit-fix

v1.0.1

Published

This GitLab CI CLI runs npm audit fix and creates a merge request

Readme

gitlab-npm-audit-fix

This GitLab CI CLI runs npm audit fix and creates or updates a merge request.

GitLab-oriented TypeScript port of the GitHub Action ybiquitous/npm-audit-fix-action.

It keeps the same high-level flow:

  1. run npm ci
  2. collect npm audit --json
  3. run npm audit fix
  4. run npm ci again
  5. aggregate package changes
  6. commit + force-push a branch
  7. create or update a merge request

GitHub-specific behavior is adapted to GitLab using @gitbeaker/rest.

Usage

gitlab-npm-audit-fix --gitlab-token "${GITLAB_TOKEN}"

Inputs (action-compatible, GitLab-adapted)

  • --gitlab-token GitLab token (default: GITLAB_TOKEN or CI_JOB_TOKEN)
  • --gitlab-user Git user name for commit changes
  • --gitlab-email Git user email for commit changes
  • --branch created branch (default: gitlab-npm-audit-fix)
  • --default-branch default branch (auto-detected when omitted)
  • --commit-title commit message and merge request title
  • --labels labels for merge request (comma-separated)
  • --assignees assignees for merge request (comma-separated usernames)
  • --npm-args extra arguments for npm commands
  • --path path to the project root directory
  • --merge-request-template-file path to merge request template file (optional, default: none)
  • --merge-request-template-placeholder placeholder token for report injection (default: <!-- gitlab-npm-audit-fix:report -->)

Behavior:

  • Adds a severity label automatically based on the highest fixed vulnerability severity (severity::critical, severity::high, severity::moderate, severity::low, or severity::info).
  • If the template file is missing, the tool falls back to the generated merge request body.

GitLab CI example

npm_audit_fix:
  image: node:24
  before_script:
    - cd webui
  script:
    - npx gitlab-npm-audit-fix --gitlab-token "${GITLAB_TOKEN}"