Expand description
What the lint tools a configuration names currently resolve to.
A code-block tool’s verdict depends on which binary runs, so a cached lint
result is only valid for the binaries that produced it. The fingerprint
records, for every binary a lint run could call, where it resolves on PATH
and the identity of the file there (its target through any symlinks, its size
and its modification time), or that it is missing. Installing, removing,
upgrading or re-ordering a tool on PATH changes the fingerprint.
It is a proxy, not a version: a wrapper that picks the real binary at run
time (a mise or asdf shim, npx, uvx) keeps its identity when the version
behind it changes.
Functions§
- lint_
tools_ fingerprint - The fingerprint of every binary the
lintslots ofconfigcould run.