Repository navigation
fix: repair links identified in weekly checker reports - #392
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
TippyFlitsUK
approved these changes
Oct 26, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
📝 Description
Repair the actionable links identified in eight weekly reports from 6 September–25 October 2026. The latest report (#376) includes a deleted FWSS Solidity source file, an incomplete CID example extracted as a URL, recurring Geo Web TLS failures, and recurring Cha-Ching timeouts.
Type: Bug fix
🛠️ Key Changes
service_contracts/src/modules, following the v1.5.0 move from a single Solidity contract to modules.https://cid.contact/routing/v1/providers/prefix. The anchored pattern leaves populated provider-lookup URLs checked.The CID prefix failed in all eight reviewed reports; Geo Web failed TLS in the latest three. Cha-Ching timed out in the latest five but returned HTTP 200 during verification, so it remains checked without an exclusion.
Reporter improvements are tracked separately in #391. This PR does not automatically close #376 because a complete weekly scan has not been rerun.
🧪 How to Test
git diff --check.The full scheduled Lychee scan was not run locally; validation targeted the changed destinations and reported failures.
🔖 Resources