Fictional cross-chain bridge with a public security roadmap and a previously disputed milestone.
[](https://shiptrace.vercel.app/projects/bridgeforge)
Paste into a README or docs page. The badge updates automatically and links back here.
Ship Score
Ship Score · formula v1.0.0
60–79 · Mostly documented delivery
This score measures documented delivery, not investment quality.
Importance-weighted credit for approved milestones whose deadlines have passed.
Release/tag cadence and weekly activity continuity from public repositories; not raw commit counts.
Rolling success rate of timestamped checks against explicitly listed product endpoints.
Dated roadmap updates, published explanations, accessible documentation and change disclosure.
Hierarchy-weighted quality and completeness of accepted evidence.
Read the full methodology. Snapshots are stored with raw component values and are never rewritten.
Score history
6 stored snapshots
| Date | Total | Formula |
|---|---|---|
| 16 Apr 2026 | Insufficient data | v0.9.0 |
| 16 May 2026 | Insufficient data | v0.9.0 |
| 15 Jun 2026 | Insufficient data | v1.0.0 |
| 15 Jul 2026 | Insufficient data | v1.0.0 |
| 14 Aug 2026 | 78 | v1.0.0 |
| 13 Sept 2026 | 77 | v1.0.0 |
Roadmap
5 commitments recorded from cited public sources, ordered by deadline.
deadline 7 Mar 2026 · 6 months ago · delivered 25 Feb 2026
deadline 26 May 2026 · 4 months ago · delivered 5 Jun 2026
deadline 25 Jul 2026 · 51 days ago · delivered 27 Jul 2026
deadline 24 Aug 2026 · 21 days ago
deadline 22 Sept 2026 · in 8 days
Open commitments
Deadlines that have not passed. Community evidence can be submitted at any time.
Commitment (paraphrase) · Integrate one additional supported chain.
Commitment recorded from cited source (Bridgeforge roadmap), accessed 2026-07-30.
Mara Okafor · 31 Jul 2026 09:00 UTC · audit ST-4A80CBEC
Verified from public evidence
3 milestones verified as shipped or partially shipped.
Commitment (paraphrase) · Deploy bridge version 2 with upgraded verification.
Commitment recorded from cited source (Bridgeforge roadmap), accessed 2025-10-08.
Mara Okafor · 9 Oct 2025 09:00 UTC · audit ST-A9F80FB4
Project published a dated progress update.
Mara Okafor · 22 Dec 2025 16:00 UTC · audit ST-A9F80FB5
Evidence submitted for review.
SHIPTRACE automated intake · 24 Feb 2026 15:00 UTC · audit ST-A9F80FB6
Verified from public evidence: primary source matches the commitment scope.
Mara Okafor · 25 Feb 2026 15:00 UTC · audit ST-A9F80FB7 · 1 evidence ref
Commitment (paraphrase) · Form an independent security council with published members and powers.
Moderator note · Initially disputed because member list was not public; resolved after the project published members and a charter.
Commitment recorded from cited source (Bridgeforge roadmap), accessed 2025-12-27.
Mara Okafor · 28 Dec 2025 09:00 UTC · audit ST-F8DC6AC4
Project published a dated progress update.
Mara Okafor · 12 Mar 2026 16:00 UTC · audit ST-F8DC6AC5
Community dispute opened: council member list not public at time of verification.
Mara Okafor · 31 May 2026 12:00 UTC · audit ST-F8DC6AC8
Evidence submitted for review.
SHIPTRACE automated intake · 4 Jun 2026 15:00 UTC · audit ST-F8DC6AC6
Verified from public evidence: primary source matches the commitment scope.
Mara Okafor · 5 Jun 2026 15:00 UTC · audit ST-F8DC6AC7 · 1 evidence ref
Dispute resolved: project published charter and member list. Prior decision preserved in history.
Mara Okafor · 7 Jun 2026 12:00 UTC · audit ST-F8DC6AC9 · 1 evidence ref
Commitment (paraphrase) · Add configurable rate limits on withdrawals for all supported assets.
Moderator note · Rate limits documented for the two largest assets only.
Commitment recorded from cited source (Bridgeforge roadmap), accessed 2026-04-06.
Mara Okafor · 7 Apr 2026 09:00 UTC · audit ST-3FA9B51D
Project published a dated progress update.
Mara Okafor · 31 May 2026 16:00 UTC · audit ST-3FA9B51E
Evidence submitted for review.
SHIPTRACE automated intake · 26 Jul 2026 15:00 UTC · audit ST-3FA9B51F
Verified from public evidence: partial scope delivered. Rate limits documented for the two largest assets only.
Mara Okafor · 27 Jul 2026 15:00 UTC · audit ST-3FA9B520 · 1 evidence ref
Neutral record
A missed deadline or missing evidence is recorded as such. It is not a conclusion about the project's intent.
Commitment (paraphrase) · Enable yield on bridged assets.
Moderator note · No qualifying evidence found as of the last check.
Commitment recorded from cited source (Bridgeforge roadmap), accessed 2026-06-05.
Mara Okafor · 6 Jun 2026 09:00 UTC · audit ST-EAF3979D
No qualifying evidence found as of 2026-08-27.
Mara Okafor · 27 Aug 2026 23:00 UTC · audit ST-EAF3979E
Automated observation
Repository activity is an observation, not proof of delivery. Commit counts alone never verify a milestone.
Automated observation
One failed check never proves abandonment. Availability uses a rolling window with neutral labels.
Sources
Accepted evidence is verified; pending community submissions are visibly unverified until a moderator decides.
Docs list limits per asset with an effective date.
Moderator conclusion · Source is a public, dated record matching the commitment scope.
Audit record ST-60A0E30B · database identifier, not a blockchain claim
Docs page listing council members, powers and publication date.
Moderator conclusion · Source is a public, dated record matching the commitment scope.
Audit record ST-6F837D72 · database identifier, not a blockchain claim
Tagged release with deployment addresses.
Moderator conclusion · Source is a public, dated record matching the commitment scope.
Audit record ST-79CEEA22 · database identifier, not a blockchain claim
Audit trail
Every verified status change, new commitment, deadline change and accepted evidence for this project.
Corrections
Statuses are set only by moderators, with a written reason and evidence references, following the published methodology. Automated checks create observations, never conclusions.
Project claims, community submissions, automated observations and moderator conclusions are labelled separately throughout this page.
Believe something here is wrong? Anyone — including project representatives — can request a correction. Prior decisions remain in the audit history.
