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

oxlint-suggestion-action

v1.0.1

Published

A template to create custom GitHub Action with TypeScript/JavaScript.

Readme

oxlint-suggestion-action

Build Test Oxlint CodeQL

This GitHub Action runs Oxlint and provides inline feedback on the changes in a Pull Request. Features:

  1. It posts review comments for Oxlint diagnostics on modified lines.
  2. It only provides feedback for lines changed in the Pull Request, so pre-existing issues outside the diff do not add noise.

(If you use ESLint you should consider this GitHub Action for similar features.)

Examples

When there is any Oxlint warning or error, this action will leave a comment:

example-screenshot

Usage

Set up a GitHub Action like this:

name: Oxlint

on:
  push:
    branches: [main] # or [master] if that's the name of the main branch
  pull_request:
    branches: [main] # or [master] if that's the name of the main branch

jobs:
  oxlint:
    runs-on: ubuntu-latest
    permissions:
      contents: read
      pull-requests: write

    steps:
      - uses: actions/checkout@v6
      - uses: actions/setup-node@v6
        with:
          node-version: '24'
          check-latest: true

      - name: Install dependencies
        run: yarn install # or npm ci if you use npm and have package-lock.json

      - uses: CatChen/oxlint-suggestion-action@v1
        with:
          request-changes: true # optional
          fail-check: false # optional
          github-token: ${{ secrets.GITHUB_TOKEN }} # optional
          directory: './' # optional
          targets: '.' # optional
          oxlint-bin-path: './node_modules/.bin/oxlint' # optional
          config-path: '' # optional

Save the file to .github/workflows/oxlint.yml. It will start working on new Pull Requests.

Options

request-changes

This option determines whether this GitHub Action should request changes if Oxlint does not pass. This option has no effect when the workflow is not triggered by a pull_request event. The default value is true.

fail-check

This option determines whether the GitHub workflow should fail if Oxlint does not pass. The default value is false.

github-token

The default value is ${{ github.token }}, which is the GitHub token generated for this workflow. You can create a different token with a different set of permissions and use it here as well.

directory

The default value is './'. This action runs Oxlint from this directory.

targets

The default value is '.'. For example, it could be 'src' or 'src/**/*.ts' for a typical TypeScript project. You can use glob patterns to match multiple directories, for example '{src,lib}'.

oxlint-bin-path

The default value is './node_modules/.bin/oxlint'. This action uses the Oxlint binary from this path.

config-path

The default value is an empty string. Oxlint's default config discovery is used when this value is empty. If your config file is in a non-default location, set this option.

FAQ

Can I have GitHub suggestions outside of the scope?

No, mostly not. GitHub only allows review comments inside diff hunks (changed lines and a small surrounding context). For consistency, this action only comments on changed lines in the Pull Request.

How can I avoid having annotations in generated code inside a project?

Follow GitHub's documentation and use .gitattributes to mark generated files and directories correctly. GitHub will hide those files in Pull Requests.