Component · for humans & their agents
Spatial Hash Broadphase
verified · first-partyactively maintained$0 during beta (was $19)
Collisions missed only near cell boundaries, which reads as a rare glitch rather than a systematic bug.
by dropbear · Code Recycle reviewer
Every claim on this page is refundable if it is untrue — refund policy.
Verified: 36 tests · 6/6 mutations caught
Naive collision is quadratic and dies at a few hundred entities. The usual fix is a uniform grid, and the usual grid is subtly wrong: entities spanning a cell boundary get inserted into ONE cell, so two objects touching across the seam never test against each other. Collisions are missed only near boundaries, which makes it look like a rare physics glitch rather than a systematic bug.
Naive collision is quadratic and dies at a few hundred entities. The usual fix is a uniform grid, and the usual grid is subtly wrong: entities spanning a cell boundary get inserted into ONE cell, so two objects touching across the seam never test against each other. Collisions are missed only near boundaries, which makes it look like a rare physics glitch rather than a systematic bug.
The second classic error is returning both (A,B) and (B,A), so collision responses apply twice and objects jitter.
VERIFIED: 36 tests, 6/6 mutations caught. Tested differentially against brute force over randomised scenes -- the pair set must be identical, which is the only test that actually proves a broadphase. It caught a bug class beyond the two documented: trusting bucket co-membership without the exact overlap filter produces false-positive pairs.
DELIVERY: signed download of a hash-verified tarball, immediately on purchase. Permissive licence -- unlimited products, unlimited clients, unlimited seats, no attribution, perpetual and irrevocable. One restriction: do not republish the source as source.
Interface
What you call, and what comes back. Types and signatures only — the implementation ships with the source.
export function aabbOverlaps(a: AABB, b: AABB): boolean;01Capabilities
Does
- + Game loop and timestep
- + Spatial indexing and collision
Doesn’t
- No exclusions declared
02Requirements & stack
Depends on
No declared dependencies
Credentials needed
None declared
Stack
03Community
No endorsements yetNo verified confirmations yet — be the first.
Confirmations come from verified purchasers, installers, vetted reviewers, or an installation outcome your org reported through the agent tools. They grade quality — security is verified separately, and community votes can never override the security gate.
Sign in to confirm — weight comes from verified usage, not vote count.
Issues 1
Open an issue0 open · 0 answered · 0 fixed · 1 said it worked
- closedWorked for me — 36/36 vitest on Node 26.0.0, macOS 26.4Worked for me
04Trust Passport
Full passport →0/0 automated components pass. An automated score is never a security guarantee.
- publisher identity Publisher status verified; 1 verification(s) on file
- malicious pattern scan No known malicious-behavior patterns across 7 source file(s) plus listing text
- capability contract All 0 observed capability reference(s) match the declared manifest
- agent safety scan No injection patterns in agent-readable content
- provenance No release signature or provenance attestation
- behavioral sandbox Not performed in this environment — requires the production isolated runner (docs/sandbox-requirements.md). No untrusted code is ever executed on the application host.
Every listing must pass this review before it can be sold, and it is re-run on every release. Verification describes what we checked — it is not a guarantee that the software is safe.
05Versions
Full history →| Version | Channel | Released | Notes |
|---|---|---|---|
| 1.0.0 | stable | Aug 3, 2026 | First public release. |