Skip to main content

Dependency override register

Tayho treats root dependency overrides as temporary, security-qualified controls. An override may be removed only after every direct owner has published a non-vulnerable compatible constraint and the frozen lockfile, workspace suite, Ponder runtime qualification, and four production image scans remain green without it. Qualification commands:
The release workflow additionally rebuilds and scans the keeper, indexer, API, and market-data images with pinned Grype. Do not add ignore rules to compensate for an override regression. The root package.json and frozen bun.lock are authoritative. Update this register in the same change as any override addition, version change, or removal.

Temporary OSV exceptions

osv-scanner.toml contains advisory-specific exceptions only when the latest direct upstream package still pins a vulnerable transitive version and Tayho does not expose the affected code path. Every exception has a reason and an expiry date. Package-wide or non-expiring exceptions are prohibited. As of 2026-07-24, Ponder 0.17.1 requires Hono Node Server 1.x and fails its runtime qualification under Hono 2.x. Mintlify 4.2.740 retains several advisory-affected packages solely in the repository documentation toolchain. These exceptions expire on 2026-08-31 and must be removed earlier when the respective latest upstream release resolves them.
Last modified on July 24, 2026