[dependabot]

Bumps the npm group with 2 updates: knip and ata-validator.

Updates knip from 6.44.0 to 6.44.1

Release notes

Sourced from knip's releases.

Release 6.44.1

• Narrow the docs package Node.js engine range to Astro's requirement (60589c42a12b8f26c048318017700f56cbe9bbef)
• Follow resolve.alias in the Rsbuild plugin (#2251) (4dc61d2febaa15770f41d8a5af7d33f19de25fa3) - thanks @​fixfon!
• Read SWC plugins from tools.swc in the Rsbuild plugin (#2253) (ad2227a52970044d727e08a73b22e9ebea811dd1) - thanks @​fixfon!
• Read .release-it.mjs and other c12 extensions in the Release It plugin (#2258) (87816e6f311510c139e998b2b956aed612239b1d) - thanks @​SwastikTripathi!
• Read .mocharc.mjs in the Mocha plugin (#2259) (16fee14f4ec1bcd3244a1b4cb2ac15343a4e0999) - thanks @​SwastikTripathi!
• Restart the language server on config changes after a failed start (#2257) (f7db448226066f61ee6ee7e938cdc683bbbf433f) - thanks @​fixfon!
• Keep the command after boolean flags in the Bun resolver (resolve #2262) (3c84cafb68b2fa3d419b03a3a5e564d60aaeef30)
• Read babel.config.mts in the Babel plugin (#2267) (04abfd84887e57eeb5dd8e8a9044cd3aa405ad8c) - thanks @​clean99!
• Track import().then() callback member usage (#2264) (14565eb56ec16140d30708fa498c8b34f23c1f9f) - thanks @​gioboa!
• Reload the knip config file when the language server restarts (#2261) (fa9ca71a9a67f017e2cf209725f4ab7aa726c220) - thanks @​fixfon!
• Read all supported CSpell configuration locations (#2265) (c6c5b2cbf6a96abef70f6f30301fc67a0f56a6cd) - thanks @​clean99!
• Read SVGR configs from cosmiconfig search locations (#2266) (47082a803eb776166cf39399c1e4e06a737c91e7) - thanks @​clean99!
• Handle extends arrays in the npm-package-json-lint plugin (#2269) (83c8c80a50e0d77babc5422c059ef86c53a2e548) - thanks @​clean99!
• Read Relay configuration from package.json (#2270) (6ce8b0050006251148b3bbc42989bb430ed484ec) - thanks @​clean99!
• Read dependencies from SWC config arrays (#2271) (5ffe9276e8a54ba00035976ad8dfe394535b9f50) - thanks @​clean99!
• Recognize CJS and ESM data files in the Eleventy plugin (#2272) (d939417b0ea7660eae1a119d5e2ddd0aedeadca1) - thanks @​clean99!
• Unroll case iterations in the SolidJS Vite, Buf, Eve and Nx plugin tests (5f87aabe082b3dc0db5a77d7c37119caa9b31fb3)
• Hoist remark to the root for the VS Code remark extension (e7772700fb26260fc877e7d66b30005b1acdfef6)
• Format root Markdown and package READMEs with pnpm remark (58c7670cfb255c395b6dfec0b70b1f25a0860d47)
• Write readable tests (393b34864396372bd9b90ab50de96c0628ad5d91)
• Format Markdown with remark (10c0133f697bcaecb17833094749178fb5d5f594)
• Fix local links in Markdown (a3fd031d853f9ed55cd952a4211c75d43840c921)
• Treat cloudflare: specifiers as runtime built-ins (#2268) (e7f261e82b0a310141aea03956d52d218929c518) - thanks @​SwastikTripathi!

Commits

• da07b6e Release knip@6.44.1
• e7f261e Treat cloudflare: specifiers as runtime built-ins (#2268)
• 10c0133 Format Markdown with remark
• 5f87aab Unroll case iterations in the SolidJS Vite, Buf, Eve and Nx plugin tests
• d939417 Recognize CJS and ESM data files in the Eleventy plugin (#2272)
• 5ffe927 Read dependencies from SWC config arrays (#2271)
• 6ce8b00 Read Relay configuration from package.json (#2270)
• 83c8c80 Handle extends arrays in the npm-package-json-lint plugin (#2269)
• 47082a8 Read SVGR configs from cosmiconfig search locations (#2266)
• c6c5b2c Read all supported CSpell configuration locations (#2265)
• Additional commits viewable in compare view

Updates ata-validator from 1.61.3 to 1.62.0

Release notes

Sourced from ata-validator's releases.

1.62.0

A security and correctness release: an outside scan of the repository reported 104 findings, each was reproduced before it was fixed, and about seventy were real. Every fix has a test that fails on 1.61.3. Upgrading changes no API.

Two of them are security issues and have advisories:

• A schema whose numeric keyword held a string instead of a number (minimum: '0||(...)') had that string run as code when the validator was built. Affects applications that compile schemas from others; versions 0.4.15 to 1.61.3.
• A $ref pointer such as #/allOf/abc aborted the process from the native engine. Same condition, same versions.

The rest, briefly:

• Validation accepted documents it should reject in several places: a type inside allOf dropped when the parent declared another, inherited names counted as evaluated under unevaluatedProperties, and on the native buffer path a false schema letting null through, primitive enums letting containers through, more than 64 required names, counts past 2^32, patterns RE2 cannot run, and email, date, uri, ipv4, ipv6 and hostname checks looser than the JavaScript ones. The native checks now follow lib/formats.js and agree with it on 34,000 strings.
• Inputs that took seconds or gigabytes now take milliseconds: reading .errors for an object with 20,000 unexpected keys (19.6 s to 5 ms), uniqueItems over crafted numbers (1.75 s to 3 ms), a long key across many failing items on the native path (3.9 GB), the defaults pass on a backtracking patternProperties key, and several schema-driven blowups in the tools.
• Worker threads registering schemas at once no longer corrupt the native registry.
• ata-validator/stream, new in this release: a JSON array or NDJSON validated record by record as the chunks land. A 100 MB body with a bad third record is refused in 13.5 ms and 122 MB instead of 517 ms and 783 MB, and a Node http request is left open so the 400 reaches the client.
• uuid checks read class tables: 85 to 35 ns.

Speed is unchanged: every row of the regression gate is within the run-to-run spread against 1.61.3, and a phone-profile page reaches its first validated result in the same 790 ms. The browser runtime's first load is 764 bytes larger gzipped.

Not fixed, and stated in SECURITY.md: the buffer APIs accept malformed JSON inside a value the schema never reads, since checking it would read every accepted document in full; and the interpreted engine runs a pattern with a \p{...} escape on the platform RegExp, which can backtrack.

The full list is in CHANGELOG.md.

Changelog

Sourced from ata-validator's changelog.

• 1.62.0 made a schema compile about 2% slower: the check that refuses a non-numeric value in a numeric keyword looked up thirteen keywords on every schema node. It now reads the node's own keys. A nine-field zod schema through @ata-project/zod compiles in 159.7 µs against 160 on 1.61.3 and 161.2 on 1.62.0, medians of 15 interleaved rounds.

1.62.0 - 2026-10-31

Added

• ata-validator/stream and v.stream(opts): validation as the body arrives. A JSON array or NDJSON fed in chunks is split without being parsed as a whole, a scan that tracks strings and nesting for the array, newlines for NDJSON, and each record is parsed and validated the moment its last byte lands; the first failing record is reported then, with the errors validate() gives for it, and validateStream(v, source) stops a Node Readable or a Web ReadableStream there instead of reading it to the end. A Node http request is left open and the rest of its body is read and dropped rather than destroyed, so the 400 the handler writes reaches the client: with the socket closed, Node's fetch saw write EPIPE and Chrome "Failed to fetch" instead of the answer; left open, Node's fetch read the 400 after 24 ms and 1 MB of a 100 MB upload. On a 100 MB body of 128,419 order documents with the third invalid: 517 ms and 783 MB (read it all, JSON.parse, validate the array) to 13.5 ms and 122 MB, having read 0.1 MB; with the last record invalid the time is the same and the memory a third. onRecord hands each passing record over parsed; stopOnFirst: false lists every failure. tests/test_stream.js holds the stream to whole-document validation under every chunk cut.

Changed

• The uuid format reads two class tables, the class of a character and the class each of the 36 positions wants, and ORs the mismatches instead of branching on every character; the generated code hoists the same tables once per compiled function (_uu) and the standalone modules carry them. On the 900 ids of the order body in validator-benchmarks: 85 to 35 ns a check; the order body's verdict 269 to 229 ns a document on the runtime, 270 to 232 in the module from ata build. tests/test_uuid_table.js holds the runtime, the hoisted and the inline forms to the 8-4-4-4-12 rule for every code point at every position.

Fixed

An outside scan of the repository reported 104 findings. Each was reproduced before it was fixed; the ones below were real. Each has a test that fails on 1.61.3.

Code ran or the validator accepted what it should reject:

• A schema's numeric keyword given as a string (minimum: '0||(...)') was written into generated code and ran when the validator was built, through $ref targets, the compat shim and ata build too. Such a schema is now declined by the code generator. tests/test_schema_code_injection.js.
• A type inside allOf or dependentSchemas was dropped when the parent declared a different one: {type: 'number', allOf: [{type: 'integer'}]} accepted 1.5, in generated code and in standalone modules.
• unevaluatedProperties: false beside patternProperties counted inherited names (constructor, __proto__) as evaluated; a patternProperties key such as ^a.b was read as the literal prefix a.b; a property named /x or __proto__ broke the standalone module's error path and the scanner.
• Two caller formats whose names differ only in punctuation (foo-bar, foo_bar) shared one check; format: '', an inherited name (constructor) and a caller format over a built-in name were answered differently by the engines.
• The interpreted engine accepted, from its 1001st call, a document a not rejected when the schema listed required names next to additionalProperties.
• Coercion to an array could turn an inherited constructor into an own property and satisfy required; removeAdditional and coercion reached into inherited objects.
• parse() could return an object validate() rejects: a required name the copy dropped, defaults that completed an if, prefixItems positions, a default with a __proto__ key, a $ref inside an embedded $id. It now declines the copy or checks the finished one.
• The cold-start engine ignored a schema added with addSchema() for its first 64 calls; an extension check on validateJSON read the text instead of the defaulted document; strictSchema skipped schemas given as JSON text.
• The native engine behind the buffer APIs (isValid, isValidNDJSON, isValidParallel, countValid, and validateJSON above 8 KB) accepted documents validate() rejects: a false schema let null through, an empty enum and a primitive enum let containers through, more than 64 required names saturated a bitmask, $dynamicRef was skipped on the On-Demand path, counts above 2^32 wrapped, patterns RE2 cannot take (lookaround, backreferences) were dropped, a property name with a quote matched across members, and email, date, uri, ipv4, ipv6 and hostname were looser than the JavaScript checks (ipv6 accepted any string with a colon). The six checks now follow lib/formats.js and agree with it on 34,000 strings in tests/test_native_formats.js; formats the engine has no check for, a caller's own formats and propertyDependencies go through validate(). tests/test_native_findings.js.

The process crashed, hung or ran out of memory:

• A $ref pointer segment such as #/allOf/abc aborted the process from the native engine.
• Worker threads registering schemas at the same time corrupted the native registry, and the native thread pool could return before its work was done.
• In first-error mode the native walker kept visiting every failing array item, each error carrying its own copy of the path: a 234 KB document took 3.9 GB.
• $dynamicRef scopes across embedded resources made generated code grow as 2^n; sixteen layers overflowed the stack.
• Patterns with very large counted repeats (a{100000000}) exhausted memory in the regular expression compiler; nested ones grew multiplicatively.
• uniqueItems hashed numbers below 1e-9 alike, so crafted arrays compared every pair: 16,000 objects took 1.75 s, now 3 ms.
• Reading .errors for an object with many unexpected properties counted its keys once per error: 20,000 keys took 19.6 s, now 5 ms. Sorting long error lists, the defaults pass over repeated $refs, the scanner over wide allOfs, describeSchema, toTypeScript, the Bun target, ata verify, ata migrate and the HTML escaping of ata build output each had a quadratic or exponential case and are bounded now.
• The defaults pass matched patternProperties keys with the backtracking RegExp even where validation used the linear engine: a 29-character key took 1.2 s.
• ata build hung when its inputs shared only the filesystem root, and --watch rebuilt forever when the cache file sat in a watched directory.

Output a caller or another tool reads:

• A source map's line and column, a file name in the Bun target and in ata migrate's report, and property names printed by the command line are escaped; a schema string in a toTypeScript comment can no longer end the comment.
• A JSON error's dataFrame.text held the whole source line for every error; past 200 characters it is now an excerpt around the value, with textCol giving the value's column in it.
• ata build's cache reused a module built with source: true for a source: false build.
• validateStream(v, req) destroyed a Node http request at the first failure, closing the socket under the response, so the client saw a network error instead of the 400. Reading now stops and the rest of the body is drained.

Not fixed: the buffer APIs still accept malformed JSON inside a value the schema never reads ({"a": tru} under a schema about b only), because checking it costs every accepted document a full read of the text. The interpreted engine still runs a pattern with a \p{...} escape on the platform RegExp, which can backtrack; SECURITY.md lists it.

Commits

• 02c08ba release: 1.62.0
• 8cfedd9 chore: lockfile for 1.61.3
• 79e8590 fix: the confirmed findings of an outside scan: code from numeric keywords, s...
• 5575dc8 fix: validateStream leaves a Node http request open at the first bad record, ...
• 6769761 docs: the SchemaStore distribution, 446 schemas on their own samples, in the ...
• d0e4cbd perf: the generated email helper keeps its comparison chain; the table form c...
• b8da530 feat: ata-validator/stream, validation as the body arrives; a 100 MB body wit...
• 2208c84 perf: uuid and the generated email check read class tables instead of branchi...
• 25a5f4b docs: side-by-side table from the 2026-10-30 run, typia 15.2.2 with the patte...
• c6023d9 docs: SECURITY.md says where each alert a package scanner reports comes from
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[netlify]

✅ Deploy Preview for schemabenchmarks ready!

Name	Link
🔨 Latest commit	cd365f5
🔍 Latest deploy log	https://app.netlify.com/projects/schemabenchmarks/deploys/6ae859df6c9a9fd4b4bc0c6b
😎 Deploy Preview	https://deploy-preview-400--schemabenchmarks.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.