Loading products
Builder Reports
A Builder Report analyzes one project from its source. Each finding opens the file and lines it used, states coverage, and names what the report could not check.
For imported repositories and uploaded source.
CitedCited2
PartialPartial1
Not AssessedNot Assessed1
HBR-201
The retry cap is five attempts, and the loop exits on the first successful response.
A partner outage cannot hold a worker open indefinitely.
retry.ts lines 18-27
Backoff timing is not exercised in the selected files.
Every finding names the file it rests on or says what was not checked. fydell does not score the project.
Evidence
A finding states what the files show, separately from what Fydell infers from them. The source sits beside the claim, with the lines it rests on and the limitation that applies.
When nothing in the selected files supports a claim, the report says so. A gap is shown as not observed or Not Assessed, never as a failing mark.
Cited at a revision
File, lines, and commit. Everyone reads the same code.
Coverage stated
How many files were read, which were skipped, and why.
Labeled by basis
Code, your statement, and reviewer notes stay separate.
Engineering PassportBackendFull-stackLumen Ledger2 projects shared
At Harbor Pay I own partner payment delivery. The webhook service keeps posts reliable with a and an . Next: show how it holds up with .
Featured project
Delivers partner payment events with bounded retries and a duplicate-event check.
dispatcher.tsdispatcher.tsdispatcher.tsretry.tsBacked by evidence
The retry loop stops after five attempts and exits on the first successful response.
retry.ts · lines 18-27In review
When an engineer shares a project from their Engineering Passport, a hiring team reads the Builder Report findings against each requirement in Hiring Workspace.
BackendLumen LedgerPartner integrations2 projects shared
What the shared work demonstrates
A webhook service that stops retrying after five attempts and skips events it has already delivered. Concurrent workers and load behavior were not shown.
Delivers partner payment events with bounded retries and a duplicate-event check.
dispatcher.tsdispatcher.tsdispatcher.tsretry.tsSelected requirement citesretry.ts · lines 18–27
Requirements
The loop stops after five attempts and exits on the first successful response.
Limits