Comparison
skif builds on three projects and covers their three jobs in one tool, with one configuration file and one report format.
| Tool | Scope | Relation to skif |
|---|---|---|
| sherif | Zero-config monorepo manifest rules | skif began as a fork; the manifest rules are ported with stable ids and skif.toml configuration, and the sherif behaviours fixed in the port are listed in the migration guide. |
| syncpack | Version consistency, semver ranges, catalogs | Same problem space; skif’s policy rules reuse syncpack’s specifier model, vendored in skif-specifier. |
| knip | Unused files, exports and dependencies | Same problem space; skif’s analysis runs on oxc, with static config extraction instead of running tools. |
| manypkg | Workspace consistency checks and fixes | Overlapping manifest checks; skif adds a rule registry, severities and a library API. |
Capabilities
Section titled “Capabilities”The tables compare skif with sherif 1.13.0, syncpack 15.3.3 and knip 6.45.1. Every cell of the other tools was
checked against their source code at those release tags, and where it depends on behaviour, by running the released
version on a test workspace (sources). A cell is Yes, No, or Partial, which the numbered note below the
table explains. The skif column describes the main branch and names the rule or command that does the work; every
rule is on the rules pages. How often skif and knip report the same findings on real repositories is
under Parity with knip.
Manifests, versions and workspaces
Section titled “Manifests, versions and workspaces”| Capability | skif | sherif | syncpack | knip |
|---|---|---|---|---|
Manifest and workspace rules: root private and packageManager, empty and unsorted dependency maps, @types in dependencies, unmatched workspace patterns, members without package.json |
Yes | Yes | Partial (1) | No |
| Version mismatches across packages | Yes: version-mismatch |
Yes: multiple-dependency-versions (2) |
Yes | No |
| Version groups and semver-range groups | Yes: [[version-groups]], [[semver-groups]] |
No | Yes | No |
| Banned dependencies | Yes: banned-dependency |
No | Yes: isBanned |
No |
Related dependencies on one version (react, react-dom) |
Yes: unsynced-dependency-family, families configurable |
Partial (3) | Yes: dependencyGroups with an aliasName |
No |
Catalog policy: catalog: used where an entry exists, dependencies missing from the catalog, entries that differ |
Yes: pnpm, Bun, Yarn 4.10+ | No | Partial (4) | No |
Unused catalog entries, unresolved catalog: references |
Yes (5) | No | Partial (6) | Yes: catalog, catalogReferences; pnpm, Yarn, Bun |
workspace: protocol for workspace packages |
Yes: workspace-protocol |
No | Partial (7) | No |
Path dependencies (file:, link:, portal:) |
Yes: local-path-dependency |
No | Partial (8) | No |
| Peer ranges the installed dev version does not satisfy | Yes: incompatible-peer-dependencies |
No | Partial (9) | No |
Toolchain pins: packageManager, engines, .nvmrc, .tool-versions, mise.toml, Dockerfiles, workflows, MODULE.bazel |
Yes: toolchain-pin-drift, member-toolchain-fields, root-package-manager-field |
Partial (10) | Partial (11) | No |
| Another package manager’s commands in Dockerfiles, workflows and shell scripts | Yes: foreign-package-manager-command |
No | No | No |
| Lockfile checks: stray lockfiles, bans and families over the lockfile, stale patches | Partial (12) | No | No | No |
package.json formatting: key order, exports conditions, shorthands |
Yes: skif format, package-json-format |
Partial (13) | Yes: syncpack format |
No |
| Newer published versions from the registry | Yes: skif update; skif update --check only reports |
No | Yes: syncpack update; syncpack update --check only reports |
No |
| Dependency inventory by group | Yes: skif list, skif json |
No | Yes: syncpack list, syncpack json |
No |
- Sorting dependency maps only:
syncpack formatsorts the keys listed insortAz, by defaultdependencies,devDependencies,peerDependenciesandresolutions. syncpack has none of the other checks. dependenciesanddevDependenciesonly, and only specifiers that parse as semver;catalog:,workspace:andfile:specifiers are skipped.unsync-similar-dependencieschecks a fixed list of ten families (tRPC, React, Next.js, Storybook, Turborepo, Prisma, typescript-eslint, ESLint Stylistic, Playwright, Lexical) within eachpackage.json, not across packages. The list cannot be changed and the rule has no fix.- A
policy: "catalog"version group (NotUsingCatalog,MissingFromCatalog) over pnpm catalogs (pnpm-workspace.yaml) and Bun catalogs (the rootpackage.json); Yarn catalogs in.yarnrc.ymlare not read. Outside such a group, a catalog entry that differs from the other instances is a version mismatch. unused-catalog-entriesandunresolved-catalog-references.unused-catalog-entriesreports nothing unless[catalog] report-unused-entries = trueis set.- Unresolved
catalog:references only, inside apolicy: "catalog"version group, as a warning (an error withstrict: true); unused entries are not reported. - A version group with
dependencies: ["$LOCAL"],dependencyTypes: ["!local"]andpinVersion: "workspace:*"pins the specifier; there is no check of its own. - An
isBannedversion group withspecifierTypes: ["file", "link"];portal:specifiers are not recognised. - A
policy: "sameRange"version group overpeeranddevreports ranges that do not overlap; it compares the declared ranges, not an installed version. root-package-manager-fieldonly: the rootpackageManagerordevEngines.packageManagerfield must be present; its value is not checked.customTypesbringpackage.jsonfields such aspackageManagerandengines.nodeinto version groups; no other file is read.stray-lockfilereads no lockfile and works for every package manager. The lockfile scope ofbanned-dependencyand of dependency families reads onlypnpm-lock.yamlformat 9 (pnpm 9 to 12);stale-patched-dependenciesreadspnpm-lock.yamlandbun.lock.yarn.lock,package-lock.jsonandbun.lockbare not read (see Lockfile).unordered-dependenciessorts dependency maps; no other formatting.
JavaScript and TypeScript analysis
Section titled “JavaScript and TypeScript analysis”| Capability | skif | sherif | syncpack | knip |
|---|---|---|---|---|
| Unused dependencies and devDependencies | Yes | No | No | Yes |
| Unlisted dependencies | Yes | No | No | Yes |
| Unlisted binaries | Yes | No | No | Yes |
| Unresolved imports | Yes | No | No | Yes |
Optional peer dependencies imported but not in dependencies or devDependencies |
Yes: unused-optional-peer-dependencies |
No | No | Yes: optionalPeerDependencies |
| Unused files | Yes | No | No | Yes |
| Unused exports and exported types | Yes | No | No | Yes |
| Unused enum members, namespace members, exports and types in a used namespace | Yes | No | No | Yes |
| Unused class members | Yes: unused-class-members, matched by name (8) |
No | No | No: dropped in knip 6 (classMembers in knip 5, off by default) |
| Duplicate exports | Yes | No | No | Yes |
| Circular imports | Yes: circular-imports, off by default |
No | No | Yes: cycles, not reported by default |
Unused package.json subpath imports and exports |
Yes: unused-subpath-imports, and unused-subpath-exports off by default (1) |
No | No | Yes: subpaths (1) |
| Test-runner mocks of modules that do not exist | Yes: stale-mocks |
No | No | No |
| Hints about stale analysis configuration | Yes: stale-js-config |
No | No | Yes: configuration hints |
| Why a file, export or dependency counts as used | Yes: skif explain-usage, --trace-dependency |
No | No | Yes: --trace-file, --trace-export, --trace-dependency |
| Production and strict modes | Yes | No | No | Yes |
| Component and template files | Yes (2) | No | No | Yes (3) |
| Custom compilers for other file types | Partial: [js.compilers], declared import patterns or one of skif’s readers, never a function |
No | No | Yes |
| Built-in plugins for tools and frameworks | 213 | No | No | 207 |
| Runs no project code while linting | Yes (4) | Yes (5) | Partial (6) | No (7) |
- Added in knip 6.45.0: unused
importsentries by default, and unusedexportssubpaths withincludeSubpathExports. skif reports theimportsentries withunused-subpath-importsand theexportssubpaths withunused-subpath-exports, which is off by default. In production mode skif reports neither, since test files may be the only importers; knip reports both. .vue,.svelteand.astro(scripts and templates),.mdx,.markoand.tsrx, and the imports of stylesheets (.css,.scss,.sass,.less,.pcss,.styl,.stylus), read without a compiler (see[js]).- Built-in import extraction for
.astro,.vue,.svelte,.mdx,.marko,.tsrx,.css(Tailwind),.less,.sass,.scss,.styl,.stylus,.prismaand.md(unplugin-vue-markdown); a custom compiler can replace any of them. - Tool configurations are read statically (ADR 0001);
a package whose configuration skif cannot read is listed under
incomplete-packagesin the JSON report. After writing,--fixandskif updaterun the package manager’s install, which runs the project’s install scripts;--no-installskips it. - sherif reads only
package.jsonandpnpm-workspace.yaml. When--fixchanges a file it runsnpm install,yarn install,pnpm installorbun install;--no-installskips it. - syncpack reads no tool configuration and never runs the package manager, but its own configuration file, when it
is JavaScript or TypeScript (
.syncpackrc.{js,ts,mjs,cjs},syncpack.config.{js,ts,mjs,cjs}), is imported by anodeprocess. - knip’s plugins load configuration files such as
vite.config.tswith jiti, and knip exits2when one fails to load. - knip 5 resolved each read with TypeScript’s language service. skif has no type checker: a read of a property of the member’s name on any object counts. It leaves alone the members of decorated classes, of classes that extend an unknown class and of interfaces declared elsewhere, where knip judged them by their references (ADR 0009, ADR 0010).
Fixing, adoption and configuration
Section titled “Fixing, adoption and configuration”| Capability | skif | sherif | syncpack | knip |
|---|---|---|---|---|
| Autofix | Yes: --fix |
Yes: --fix |
Yes: fix, format, update |
Yes: --fix |
| Safe and unsafe fix levels, file deletion opt-in | Yes: --fix-unsafe, --allow-remove-files |
No | No | Partial (1) |
| Fix only some issue types | Yes: --fix-type |
No | No (2) | Yes: --fix-type |
| Preview fixes as a diff | Yes: --fix --dry-run |
No | Partial (3) | No |
| Baseline that can only shrink | Yes: skif baseline write, prune, check |
No | No | No (4) |
| Ignores with a recorded reason | Yes: reason, --require-ignore-reasons |
No | Partial (5) | No |
| Configuration translated from the other tools | Yes: skif migrate from sherif, syncpack and knip |
No | No | No |
| Configuration format | TOML: skif.toml, .skif.toml |
sherif key in the root package.json, CLI flags |
.syncpackrc, .syncpackrc.{json,yaml,yml,js,ts,mjs,cjs}, syncpack.config.{js,ts,mjs,cjs}, package.json#syncpack or #config.syncpack |
knip.json, knip.jsonc, .knip.json, .knip.jsonc, knip.ts, knip.js, knip.config.ts, knip.config.js, package.json#knip |
| Configuration layered across directories | Yes (6) | No | No | Partial (7) |
| JSON Schema for the configuration | Yes: skif schema |
No | Yes: schema.json in the npm package |
Yes |
--allow-remove-filesis needed to delete files; there are no other levels.fixselects dependencies (--dependencies,--dependency-types,--specifier-types), not issue types.--dry-runoffix,formatandupdatelists the changes without writing them; it prints no diff.- knip’s guide to gradual adoption builds an “actionable baseline” by fixing configuration gaps and caps CI with
--max-issues; no file records accepted findings. - Version, semver and update groups with
isIgnoredtake an optionallabel, free text shown as the group’s heading. skif.tomlfiles merge from the root up to the git root,extendsnames more, and[[overrides]]select packages and files (Sharing configuration).- One file, with no
extends; itsworkspacesmap sets entry, project, ignore and plugin options per workspace directory or glob, whilerules,include,exclude,compilers,tagsandcyclesare set for the whole run.
Output and integrations
Section titled “Output and integrations”| Capability | skif | sherif | syncpack | knip |
|---|---|---|---|---|
| Human output | Yes | Yes | Yes | Yes |
| JSON | Yes | No | Partial (1) | Yes |
| SARIF | Yes | No | No | Yes |
| GitHub annotations | Yes: github, on by default under GitHub Actions |
No | No | Yes: github-actions |
| GitLab Code Quality (Code Climate) | Yes: codeclimate |
No | No | Yes: codeclimate |
| Markdown, compact, CODEOWNERS | Yes | No | No | Yes |
| Custom reporters and preprocessors | No | No | No | Yes |
| Several reports in one run | Yes: --format FORMAT=FILE, repeatable |
No | No | Yes: --output-file REPORTER=FILE, repeatable |
| Watch mode | Yes: --watch |
No | No | Yes: --watch |
| Language server | Yes: skif lsp |
No | No | Yes |
| Editor extension | No | No | No | Yes: webpro.vscode-knip on the VS Code Marketplace and Open VSX |
| MCP server | Yes: skif mcp |
No | No | Yes: @knip/mcp (2) |
| Agent skill | Yes: skills/skif |
No | No | No |
| GitHub Action | Yes: polylint/skif |
Yes: QuiiBz/sherif |
No (3) | No |
| Git hooks shipped | Yes: pre-commit, prek, Poly | No | No | No |
| Library API | Yes: the skif crate; lint, lintAsync, run in the npm package |
No | No | Partial (4) |
syncpack json, and--reporter jsonoffixandformat(one object per line);lint,listandupdateprint human output only.- The tools
knip-run(runs knip and returns its configuration hints and issues) andknip-docs(knip’s documentation), and aknip-configureprompt; the agent using them editsknip.json. JamieMason/syncpack-github-action(last released as 0.2.3) defaults to syncpack 7.2.1 and callsfix-mismatchesandlist-mismatches, which syncpack 15 rejects.- Undocumented:
knipexportsmainandknip/sessionexportscreateSession, which the language server and the MCP server use; the FAQ lists a programmatic API among the requested features knip does not have.
Support
Section titled “Support”| skif | sherif | syncpack | knip | |
|---|---|---|---|---|
| Package managers | npm, pnpm, Yarn 2+, Yarn Classic, Bun | npm, pnpm, Yarn, Bun; Yarn Classic and Yarn 2+ are not told apart | npm, pnpm, Yarn, Bun and Lerna workspaces; pnpm and Bun catalogs | npm, pnpm, Yarn, Bun; pnpm, Yarn and Bun catalogs |
| Linkers tested end to end in CI | npm (hoisted); pnpm (isolated, nodeLinker: hoisted); Yarn 2+ (Plug’n’Play, nodeLinker: node-modules, nodeLinker: pnpm); Yarn Classic (hoisted); Bun (default, linker = "hoisted", linker = "isolated") |
None: CI runs cargo test on Ubuntu; sherif reads no node_modules |
None: CI runs cargo test; syncpack reads no node_modules |
No linker matrix: committed fixtures (one with Yarn Plug’n’Play) and 16 ecosystem projects installed with pnpm, npm or Yarn |
| Package manager versions tested | Latest two majors of npm, pnpm and Yarn 2+; newest Yarn Classic 1.x and Bun 1.x | None pinned; one unit test runs the CI image’s npm install |
None: CI installs no package manager | None pinned: pnpm 10 for knip’s own repository; the ecosystem projects use their own |
| Layouts | Single packages, workspaces, nested workspaces, standalone packages below a root, -r over several roots, Rush (rush.json), Lerna, Nx integrated workspaces, Bazel (bazel run) |
One workspace root, from workspaces in package.json or pnpm-workspace.yaml; no single packages, no nested workspaces, and ** matches one directory level |
Workspaces from package.json, pnpm-workspace.yaml or lerna.json, else packages/*; --source globs replace them |
Workspaces and the directories knip’s workspaces map lists; integrated monorepos (Nx) as one workspace with hand-written entry and project |
| Runtime | Native binary; the npm package is a Node addon for Node.js 22, 24, 26 and Bun 1.x | Native binary; the npm launcher is a Node.js script with no engines |
Native binary; npm launcher (engines: Node.js 14.17+) |
Node.js 20.19+ or 22.12+; Bun through knip-bun (CI tests Bun 1.4.4) |
| Operating systems and architectures | macOS, Linux (glibc, musl), Windows; x64 and arm64 | macOS, Linux (glibc, musl), Windows; x64 and arm64 | macOS, Linux (glibc, musl), Windows; x64 and arm64 | Where oxc-parser has a native binding (macOS, Linux glibc and musl, Windows, FreeBSD and more); CI runs macOS, Linux and Windows |
| Distribution | npm, crates.io, cargo-binstall, GitHub release archives, Homebrew, Scoop, GitHub Action, pre-commit and prek, Poly | npm, GitHub release archives, GitHub Action; Homebrew (homebrew-core) | npm; crates.io up to 14.0.0 | npm |
The skif versions and operating systems per package manager are under
Supported versions, and the end-to-end matrix is the e2e job of
.github/workflows/ci.yml
(ADR 0015).
scripts/check-support-matrix.sh fails when the skif rows above, the README or the supported versions table differ
from the e2e and npm-addon matrices and the linkers of scripts/e2e/lib.sh. Lefthook needs no hook from skif: it
is configured in the consuming repository (Lefthook).
Sources
Section titled “Sources”- sherif 1.13.0: README, CLI flags, rules, workspace discovery, install after a fix, CI, GitHub Action, release archives.
- syncpack 15.3.3: README, commands and flags, configuration types, configuration files, catalog groups, workspace discovery, CI, configuration file docs.
- knip 6.45.1: issue types, CLI flags, configuration, reporters, plugins, MCP server, CI, FAQ, gradual adoption, integrated monorepos.
- Runtimes and platform packages: the
engines,bin,dependenciesandoptionalDependenciesof the compared version of each package on the npm registry.
Parity with knip
Section titled “Parity with knip”How skif’s JS analysis compares with knip 6.45:
- Coverage. Every issue type of knip 6.45 has a skif rule, 19 in all (the list is in the
migration guide), and
skif migratetranslates a knip configuration. skif reads tool configurations statically and never runs project code. - Speed. Full skif runs are timed against knip on pinned public repositories; see Performance.
- Precision. Precision and recall on a generated workspace with seeded dead code are on the benchmarks page.
- Agreement. Real repositories have no answer key, so a weekly job runs both tools on pinned public repositories and compares the findings per issue type. The agreement table, generated from the committed baseline of that comparison, gives the share of each tool’s findings the other reports too, and what is counted apart.
A package whose entry files skif cannot all know (a tool configuration it cannot read) is listed under
incomplete-packages in the JSON report. skif does not judge its unused dependencies; where the configuration’s scope
is narrowed it judges the files, exports, types and members outside that scope, and otherwise none of them (see
“Incomplete entries” under [js]). knip still reports there.
A dependency on a workspace member that nothing can import or run is not reported unused: a member whose
package.json has no main, module, exports, bin, browser, types or typings and that holds no source
file, such as a tooling, asset or style package. Such a dependency orders tasks (Turborepo’s ^build, Nx’s task
dependencies), and knip reports it. A member with one of those fields or a source file is judged as before; when it
is listed only to order tasks, add it to ignore-dependencies with a reason.
Both tools report a devDependencies entry of a package that the same manifest lists in dependencies, used or
not: the production entry installs it for development as well. skif says so in the message (“is listed in
devDependencies and in dependencies”). An optional peer dependency that the code uses counts as installed in skif
when the package lists it in optionalDependencies, or when the root or a containing package lists it in
dependencies, devDependencies or optionalDependencies (outside isolate-workspaces); knip asks only the
package’s own dependencies and devDependencies. The types that a tsconfig extended through node_modules (a
Heft rig profile) finds in its own typeRoots come with that config’s package, so they do not make the extending
package use its optional peer @types/node. knip credits webpack-cli for every webpack config, and webpack as its
peer; skif judges both by the scripts, commands and imports that run them
(ADR 0009).
A package with a reached .svelte file uses svelte, the compiler of its components; knip credits svelte only
where a file or a configuration names it. skif reads the exports of a component’s module script
(<script context="module">, <script module>) and reports the unused ones; the exports of the instance <script>
(export let) are props, not exports. knip reads only the imports of a .svelte file, so it reports none of its
exports.
The size of the remaining differences per issue type is in the agreement table.
Two differences are knip’s and stay counted, as the comparison cannot tell them apart from its data: knip reports the
members of an enum used as a whole value (passed or returned, @IsEnum(E), Object.values(E), keyof typeof E,
`${E}`), also in the file that declares it, which makes every member reachable, and knip has no esbuild plugin, so it reports the entryPoints of an esbuild
script, and the files they reach, as unused.
knip does not read the specifiers of test-runner mocks. skif does: a vi.mock, jest.mock or jest.requireActual
keeps the file it names in use, and a relative or aliased mock of a file that does not exist is reported by
stale-mocks, an error that knip has no counterpart for (skif migrate --profile exact turns it off). Such a mock
is not an unresolved-imports finding, so unresolved imports compare with knip’s unresolved.
require.resolve("./x") and import.meta.resolve("./x") return the path of a module, which code hands to what loads
the module by it: a worker pool (new Worker(require.resolve("./worker"))), a bundler loader, a plugin host. In skif
the call keeps the file it names in use, a package it names is a used dependency, and the value exports of the module
are used, as for a require() that binds nothing; unused-types reports its types that nothing else imports
(ADR 0009).
knip makes such a file an entry, so it reports neither.
skif never reports a declaration file (.d.ts, .d.mts, .d.cts) as an unused file; knip reports one that nothing
imports. A declaration file that applies without an import is an entry: a script (no top-level import or export),
whose declarations are global, or a module file that augments the global scope (declare global, export as namespace) or another module (declare module "x"), or that exports nothing and loads a module for its effect
(import "x", /// <reference path>). Any other declaration file is a module, an entry only when package.json
publishes it (types, typings, the types condition of exports), a tsconfig.json lists it in files or an
entry glob names it. Otherwise it is judged like a TypeScript module once a module imports it, so unused-types
and unused-exports report what no importer uses
(ADR 0007).
knip makes every declaration file that the tsconfig.json of a workspace compiles (its include and files) an
entry, so it reports no export or type of one and reads its imports even when nothing imports it: in a workspace
whose tsconfig.json includes src/**/*, knip judges none of the .d.ts files there that skif judges.
A namespace passed as an argument is a use of the whole module in both tools, with one exception in skif: a
test-runner spy with a literal member name (vi.spyOn(ns, "a"), jest.spyOn(ns, "a"), Jasmine’s spyOn(ns, "a"))
reads member a only, as ns.a does
(ADR 0009).
knip counts such a spy as a use of every export, so skif reports the exports that nothing else reads and knip does
not.
A lazy-component loader that returns an import() (lazy(() => import("./Page")) of react or preact/compat,
React.lazy, next/dynamic, and @loadable/component without resolveComponent) uses the default export only, in
both tools, and .then((m) => m.Page) inside it uses Page. A function returning an import() passed to any other
call (wrapLazy(() => import("./Page"))) keeps the whole module used in skif, since that call may read any export,
and skif explain-usage names the call; knip counts it as a use of default and reports the named exports
(ADR 0009).
A use of a module object as a whole (a namespace passed around, spread, indexed with a computed key or named in
typeof ns, and require("./m") or import("./m")) reaches the values of the module only. In skif it uses every value
export and none of the module’s interfaces and type aliases: those stay used when they are read by name (ns.Type) or
when the importer exports the namespace itself (export default ns, export = ns), and are reported by
unused-types otherwise. A file loaded with new URL("./x", import.meta.url) is no module object but a program of its
own, so it keeps every export used, as an entry does
(ADR 0009).
knip reports such types only under nsTypes, which is off by default, and not at all for a spread or an import().
knip merges the tsconfig paths of every workspace, so an import that only another package’s paths map resolves
for it. skif resolves an import with the configuration the importing file follows, as TypeScript does: such an import
is reported by unlisted-dependencies with the detail ForeignTsconfigPaths, a message that names the config whose
paths map it, and no advice to add a dependency. The fix is to add the mapping to the importing package’s tsconfig,
or to import the module by the name of the package that exports it. A pattern with no literal prefix (*) is not
counted, as it maps every specifier, and neither is a pattern whose targets are no source file of the workspace (one
into node_modules, or to missing files). An import of a workspace package, of a package a manifest lists or of an
installed package keeps the advice to add it to package.json.
A paths mapping named like a dependency (src/* to ./src/* beside a workspace package src, lib/* to
./src/lib/* beside an installed lib) resolves in skif as TypeScript resolves it: the mapping comes before
installed packages and workspace members, also for the paths of [js.workspaces.<dir>.paths], and an import it
leads into the package’s own sources uses no listed dependency. With the paths of knip.json, knip tries the
package first and reports the local file by unused-files; with tsconfig paths it reaches the local file but
counts the listed dependency as used. skif reports that dependency by unused-dependencies instead
(ADR 0007).
Both tools report a package that a tool config names and no manifest lists (a tsconfig extends, an Oxlint or
ESLint plugin, a Prisma generator) at the config. knip reads some of them as files to resolve, so one with an unscoped
name that it cannot find is reported as unresolved or not at all; skif reports each as unlisted, with the detail
ConfigReference. A Sass importer
that a config builds in code (sassOptions.importer from sass-alias) is not read, so the imports its aliases serve
(@import "@sass/abstracts/mixins") are reported as unlisted packages; list the alias in ignore-dependencies
("@sass/*").
A package.json script or a workflow step that runs a command after cd <dir> (cd sub && pnpm exec rspack) is
judged by knip at the script’s own package, so a binary the workspace package in sub provides is reported unlisted
there and its provider unused in sub. skif credits the command to the workspace package the directory is in.
Configuration
Section titled “Configuration”skif reads skif.toml or .skif.toml only. It does not read sherif, .syncpackrc or knip.json
configuration at lint time; skif migrate translates it once into a skif.toml (see the
migration guide). Rule ids are stable kebab-case names; rules ported from sherif list their sherif
name on the rules pages.
Performance
Section titled “Performance”Generated from the latest imported run of the bench workflow, with the dependencies of the repositories installed
and skif run as it runs by default (the knip rows) or with --no-js (the sherif and syncpack rows):
- 4.1–8.4x faster than knip (median 5.8x) for dead-code analysis, on 7 pinned public repositories where knip completes; it fails on create-t3-turbo and vue-core (on n8n and next-js it exits with an error after its report).
- up to 7.4x faster than sherif (median 3.2x), and slower on 3 of 12 targets for manifest and workspace checks (
skif --no-js), on 9 pinned public repositories and 3 generated workspaces of 50, 500 and 2000 packages. - 1.7–28.0x faster than syncpack (median 8.5x) for version-policy checks (
skif --no-js), on 9 pinned public repositories and 3 generated workspaces of 50, 500 and 2000 packages.
skif 0.7.0 against knip 6.45.1, sherif 1.13.0, syncpack 15.3.3: medians of 15 runs (5 on angular, vscode, n8n and next-js) on a GitHub-hosted runner, measured on 2026-11-17.
The benchmarks page has the tables per repository and workspace, the workflow run the numbers come from, and how they are measured.
Accuracy
Section titled “Accuracy”The results on generated workspaces with a known answer (seeded manifest defects, seeded dead code), and how to reproduce each, are on the benchmarks page. The agreement with knip on real repositories is under Parity with knip.