Recordsnpm@types/bcryptjsfailure issue
Failure signature
PROJECT_COMPILE exit 2 TS2561 ×4
app/api/politicians/[id]/real-estates/route.ts(<n>,<n>): error TS2561: Object literal may only specify known properties, but <str> does not exist in type …
Evidence quality: complete · typescript/tsc · compiler-diagnostic · First recorded: 2026-09-01 · Last seen: 2026-09-01
sha256:5f96e966539e…
Where it was measured
PASS means the release recorded a passing observation at PROJECT_COMPILE and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- 2.4.6 FAIL
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 ×4 2026-09-01 → 2026-09-01
Nearest known PASS/FAIL boundaries
No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.
Evidence gaps
- No release in this window recorded a passing observation at PROJECT_COMPILE.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- @types/bcryptjs 2.4.6 This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOW MIT-0 · 2026-09-11