# framework

Cross-cutting framework identification that aggregates the `tech/*` detectors into a single, confidence-scored picture of a project's tech stack.

[`identifyFrameworks`](https://www.hyperfrontend.dev/docs/libraries/project-scope/heuristics/framework/#api-identifyFrameworks) runs frontend, backend, meta-framework, build, testing, linting, and monorepo detectors against the target project, then surfaces a [`summary`](https://www.hyperfrontend.dev/docs/libraries/project-scope/heuristics/framework/#api-FrameworkIdentification-prop-summary) string (e.g. `"React + Next.js with Jest"`), the highest-confidence [`primary`](https://www.hyperfrontend.dev/docs/libraries/project-scope/heuristics/framework/#api-FrameworkIdentification-prop-primary) framework, and per-category arrays of every detected framework with [`confidence`](https://www.hyperfrontend.dev/docs/libraries/project-scope/heuristics/framework/#api-FrameworkIdentification) and [`evidence`](https://www.hyperfrontend.dev/docs/libraries/project-scope/heuristics/framework/#api-FrameworkIdentification). `usesFramework(path, id)` is a convenience predicate for asking "does this project use Vite?" without unpacking the full identification result. Cached per project path with a short TTL; pass `{ skipCache: true }` to force fresh detection.

---

Canonical page: https://www.hyperfrontend.dev/docs/libraries/project-scope/heuristics/framework/
This file: https://www.hyperfrontend.dev/docs/libraries/project-scope/heuristics/framework.md
Documentation index: https://www.hyperfrontend.dev/llms.txt