@fastify/ajv-compiler

Build and manage the AJV instances for the fastify framework

@fastify/ajv-compiler@4.0.7 was published on 2026-10-10. Its manifest declares 3 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All @fastify/ajv-compiler versions · Permanent reference to 4.0.7

Package specifications

Version4.0.7
License declarationMIT
Published2026-10-10T10:00:57.252Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count3
Peer requirement count0
Optional dependency count0
Minified size159.06 KiB
Minified + gzip47.18 KiB
Unpacked distribution size57.47 KiB
Published file count23
Package typecommonjs
ES module entryNot declared
Default entryindex.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies7
Repository stars24
Repository forks17

Install @fastify/ajv-compiler 4.0.7

npm install @fastify/ajv-compiler@4.0.7
pnpm add @fastify/ajv-compiler@4.0.7
yarn add @fastify/ajv-compiler@4.0.7

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Binary-Artifacts10/10 — no binaries found in the repo
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Code-Review4/10 — Found 9/19 approved changesets -- score normalized to 4
Pinned-Dependencies10/10 — all dependencies are pinned
Maintained8/10 — 10 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 8
Token-Permissions10/10 — GitHub workflow tokens follow principle of least privilege
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
Security-Policy10/10 — security policy file detected
SAST6/10 — SAST tool is not run on all commits -- score normalized to 6

Evidence and freshness