Repository navigation
First release.
Added
- Stale processes: processes whose working directory is inside the project, started before an
.env*, lockfile, framework config, Python settings module or manifest changed
(/procon Linux,ps+lsofelsewhere). Wrapper chains such asnpm run devare reported once.
A small, documented table of runners that reload themselves (Vite, Next.js, Nuxt, Astro, Django
runserver,--reloadservers) downgrades those findings tomaybe. - Stale build output:
dist/ build/ out/ .next/ .nuxt/ .output/ .svelte-kit/(Node projects, nested
packages included) and Rusttarget/older than their sources. - Stale installed dependencies:
node_modulesvspackage-lock.json(version comparison against
npm's hidden lockfile),pnpm-lock.yaml(compared with pnpm's stored copy),yarn.lock(mtime only);
Python virtualenvs vsrequirements*.txt,poetry.lock,uv.lock,Pipfile.lock. - Stale generated code: Prisma, protobuf, OpenAPI client directories, GraphQL Code Generator
(codegen.yml) and user-defined[[generated]]/[[artifact]]rules in.whystale.toml. - Output: text,
--json,--markdown;--watch;--demo;--only;--strict;--no-fail. - Exit code
3when something is stale, for CI and agent hooks. - Content checks that clear false positives:
.envvalues already in the process environment,
lockfile touched but installed versions equal, Prisma schema identical to the generated copy,
requirement pins already satisfied.
Install: pip install git+https://github.com/mrzroot/whystale.git (no PyPI release yet). Note: CI workflow is not yet enabled in this repo.