ANNÁVE Lint Is Not a Linter

People keep asking if ANNÁVE Lint is something you install — like ESLint for a website. It is not. The name is on the Technical Audit I run on annave.tech/services: I check your live site over HTTP, write up what is wrong and what to fix first, and send the report async. No call, no repo access in that tier, and nothing to download.

What you actually get

I work from the public URL. Headers, SSL, metadata, canonicals, robots, sitemap, structured data, internal links, and performance signals where I run them — fifteen-plus areas in total. You receive a prioritized write-up, not a dashboard login.

Lint is the name I use for the checklist and the report shape. It is not an npm package and not a CI step you add beside ESLint.

What people mix up

The most common mistake is expecting a linter UI or a fix command. There is no “run annave lint --fix”. Another is assuming ANNÁVE Lint Deep ships with the public audit. Deep is separate: after we agree on scope, I trace findings into the codebase.

Methodology and scope: annave.tech/services/annave-lint. To request the audit: annave.tech/request.