Registry / testing / sherif-linux-x64-musl

sherif-linux-x64-musl

library1.11.1jsnpmunverified

Sherif is an opinionated, zero-config linter designed specifically for TypeScript and JavaScript monorepos. It enforces a set of rules to standardize the developer experience and prevent common regressions in multi-package repositories. The current stable version is `1.11.1`, with new minor versions being released frequently, indicating active development. A key differentiator is its performance; it's written in Rust, runs very fast, and doesn't require `node_modules` to be installed to function, making it efficient for CI/CD pipelines. It supports all major package managers including PNPM, Bun, NPM, and Yarn, and is primarily intended to be run as a CLI tool.

testing

npm install sherif-linux-x64-musl

github ↗package ↗homepage ↗

INSTALL

IMPORT

SIG · SHERIF-LINUX-X64-M

sherif-linux-x64-musl

testingjavascriptv1.11.1

Install

—

Import

—

Disk

—

Pass rate

0/ 6

Env Coverage0 / 6

glibc

18–22

musl

18–22

Install & Compatibility

Where this runs

tested against v? · npm install

Install × environment matrix

Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux

musl

node 18–226 runs

build_error

glibc

node 18–226 runs

build_error

Code

Verified usage

Verified import paths — ran on the pinned version, not inferred.

sherif (CLI)

✓ npx sherif@1.11.1

✗ import sherif from 'sherif-linux-x64-musl'

Sherif is a CLI tool and not intended for direct programmatic import in JavaScript/TypeScript. It should be executed via `npx`, `bunx`, `pnpm dlx`, or as a pre-installed binary.

Sherif Configuration

✓ /* package.json */ { "sherif": { "fix": false, "select": "highest" } }

✗ import { SherifConfig } from 'sherif-linux-x64-musl'

Configuration is provided as a `sherif` field in the root `package.json` using camelCase keys, not through a direct JS/TS import.

GitHub Action

✓ uses: QuiiBz/sherif@v1

✗ import { SherifAction } from 'sherif-linux-x64-musl'

Sherif can be integrated into GitHub Actions using the dedicated `QuiiBz/sherif@v1` action, not as a JavaScript module.

This quickstart demonstrates how to install and run Sherif in a monorepo, including an example `package.json` configuration, and how to use the `--fix` and `--select` flags for automated issue resolution.

{ "name": "my-monorepo", "private": true, "workspaces": [ "packages/*" ], "scripts": { "lint:monorepo": "sherif", "lint:monorepo:fix": "sherif --fix --select highest" }, "sherif": { "failOnWarnings": false, "ignoreRule": [ "root-package-manager-field" ] } } // To run the linter: pnpm dlx sherif@latest // To run the linter and automatically fix issues, selecting the highest version for dependencies: pnpm dlx sherif@latest --fix --select highest

sherif --version

Debug

Known issues

breakingThe official GitHub Action (`QuiiBz/sherif`) was updated to use Node.js v24. If your CI environment is still running Node.js v20 or older, this change will cause the action to fail or behave unexpectedly.

fix

Upgrade your GitHub Actions runner or `setup-node` step to use Node.js v24 or higher for the Sherif action to function correctly. Alternatively, use the `npx` method with a specific Node.js version.

affects: >=1.11.0

gotchaRunning `sherif --fix` is automatically disabled in CI environments (where the `$CI` environment variable is set). This prevents unexpected modifications to your repository in automated pipelines.

fix

To fix issues in CI, you must either run Sherif locally with `--fix` and commit the changes, or, for rules like `multiple-dependency-versions`, use the `--select highest` or `--select lowest` flag in CI to enable automated fixes without interactivity.

affects: >=1.0.0

gotchaFor non-interactive environments (e.g., CI/CD) and when using the `multiple-dependency-versions` rule with `--fix`, Sherif will prompt for version selection by default. This will cause the process to hang.

fix

Always combine `--fix` with `--select highest` or `--select lowest` when running in non-interactive environments or CI to automatically choose a version without user input.

affects: >=1.6.1

gotchaWhen configuring Sherif in the root `package.json`, the options must be provided in `camelCase` (e.g., `failOnWarnings`), whereas the equivalent CLI arguments use `kebab-case` (e.g., `--fail-on-warnings`). Mismatched casing will result in the configuration being ignored.

fix

Ensure that all options defined under the `sherif` field in `package.json` adhere to `camelCase` naming conventions.

affects: >=1.10.0

gotchaThe `sherif-linux-x64-musl` package is a specific pre-compiled binary for Linux x64 with musl libc. Directly installing this package might not work on other operating systems or architectures.

fix

For general usage, it is recommended to invoke Sherif using your package manager's `dlx` command (e.g., `npx sherif@latest`, `pnpm dlx sherif@latest`), which handles platform-specific binary selection automatically.

affects: >=1.8.0

gotchaIt is strongly recommended to pin Sherif to a specific version (e.g., `sherif@1.11.1`) in CI/CD pipelines instead of using `sherif@latest`. Using `@latest` can lead to unexpected behavior or breaking changes with new releases, potentially failing your builds.

fix

Always specify a fixed version number when running Sherif in CI, for example, `npx sherif@1.11.1` or `uses: QuiiBz/sherif@v1.11.1`.

affects: >=1.0.0

Errors

Common errors & fixes

Command 'sherif' not found

Sherif is a CLI tool and not installed globally, or the `npx`/`dlx` command was not used.

fix

Run Sherif using a package manager's executor: `npx sherif` (npm), `bunx sherif` (Bun), or `pnpm dlx sherif` (PNPM). If installed globally, ensure it's in your PATH.

Autofix is disabled in CI environments. Please run locally or use '--select' for relevant rules.

Attempting to use `sherif --fix` within a continuous integration pipeline, where automatic modifications are prevented.

fix

To enable autofix in CI for rules like `multiple-dependency-versions`, explicitly add `--select highest` or `--select lowest` to your command. For other rules, run `sherif --fix` locally and commit the changes.

Missing configuration field: 'sherif'. Expected a 'sherif' object in root package.json for options 'fix', 'select', 'noInstall', 'failOnWarnings', 'ignoreDependency', 'ignorePackage'.

The `sherif` configuration block is missing from the root `package.json`, or the field names within it are incorrect (e.g., kebab-case instead of camelCase).

fix

Add a `sherif` object to your root `package.json` with configuration options specified in `camelCase`, for example: `"sherif": { "failOnWarnings": false }`.

Multiple versions found for dependency 'react': ['18.0.0', '18.2.0']. Please choose one interactively or use '--select highest|lowest'.

The `multiple-dependency-versions` rule was triggered with `--fix` in a non-interactive environment (like CI) without the `--select` flag.

fix

When running in non-interactive contexts, append `--select highest` or `--select lowest` to the `sherif --fix` command to automatically resolve version conflicts.

Upgrade

Version history

1.11.1latest on npm

Audit

Dependencies

No dependency data recorded yet.

Agent activity

7 hits · last 30 days

node

Amazon

Resources

githubhttps://github.com/QuiiBz/sherif ↗

packagehttps://www.npmjs.com/package/sherif-linux-x64-musl ↗

homepagehttps://sherif.dev ↗