fix: getting tangled stats from our backend

[fatfingers23]

Resolves: #844

The easiest way to get a at-uri for a tangled repo is from calling their webpage and parsing it out of the HTML. Moved this to the backend to resolve the current CORS errors.

I debated adding tangled.org to the cached fetch so that the HTML response can be cached, but that seems like a pretty big cached entry and I think in prod API endpoints are cached for a while.

Test repo: @weaver.sh/editor-collab

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
npmx.dev	Ready	Preview, Comment	Feb 5, 2026 1:06pm

2 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
docs.npmx.dev	Ignored	Preview	Feb 5, 2026 1:06pm
npmx-lunaria	Ignored		Feb 5, 2026 1:06pm

[codecov]

Codecov Report

❌ Patch coverage is 0% with 1 line in your changes missing coverage. Please review.
✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
app/composables/useRepoMeta.ts	0.00%	1 Missing ⚠️

📢 Thoughts on this report? Let us know!

[coderabbitai]

📝 Walkthrough

Walkthrough

The client-side composable useRepoMeta now calls a server endpoint /api/atproto/tangled-stats/{owner}/{repo} to obtain repository metadata instead of performing HTML scraping or Constellation lookups itself. A new server route server/api/atproto/tangled-stats/[owner]/[...repo].ts was added; it fetches Tangled repo HTML, extracts an initial star count and any at‑uri, and conditionally uses a Constellation lookup to augment stars and forks. The API returns { stars, forks }, defaulting to zeros on fetch, parse or augmentation errors.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description check	✅ Passed	The pull request description clearly relates to the changeset, explaining the CORS issue with tangled stats and the decision to move logic to the backend.
Linked Issues check	✅ Passed	The PR successfully addresses issue #844 by moving tangled stats fetching from client-side to backend, resolving CORS errors and restoring stars/fork count loading.
Out of Scope Changes check	✅ Passed	All changes are scoped to resolving the tangled stats CORS issue; no unrelated modifications are present.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 3

🧹 Nitpick comments (1)

server/api/atproto/tangled-stats/[owner]/[...repo].ts (1)

49-51: Consider logging failed Constellation lookups for debugging.

Whilst silently failing is appropriate for user-facing behaviour, having no visibility into Constellation failures may make debugging production issues difficult.

💡 Optional: Add debug logging

-      } catch {
-        //failing silently since this is just an enhancement to the information already showing
+      } catch (e) {
+        // Failing silently since this is just an enhancement to the information already showing
+        console.debug('Constellation lookup failed for', atUri, e)
       }

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Missing imports will cause compilation and runtime errors.

The file uses CachedFetchResult<T> (line 17) and Constellation (line 44) but neither is imported. This will cause TypeScript compilation errors and runtime failures.

🐛 Proposed fix to add missing imports

-import type { CachedFetchFunction } from '#shared/utils/fetch-cache-config'
+import type { CachedFetchFunction, CachedFetchResult } from '#shared/utils/fetch-cache-config'
+import { Constellation } from '#shared/utils/constellation'

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	import type { CachedFetchFunction } from '#shared/utils/fetch-cache-config'
	import type { CachedFetchFunction, CachedFetchResult } from '#shared/utils/fetch-cache-config'
	import { Constellation } from '#shared/utils/constellation'

[trueberryless]

Ignore it…

[coderabbitai]

@trueberryless, understood! I'll skip this suggestion.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Validate owner and repo parameters before use.

getRouterParam can return undefined. Using undefined values directly in the URL (line 27) would result in https://tangled.org/undefined/undefined. Return an error response early if parameters are missing.

🛡️ Proposed fix to validate parameters

-  let owner = getRouterParam(event, 'owner')
-  let repo = getRouterParam(event, 'repo')
+  const owner = getRouterParam(event, 'owner')
+  const repo = getRouterParam(event, 'repo')
+
+  if (!owner || !repo) {
+    return { stars: 0, forks: 0 }
+  }

As per coding guidelines, ensure you write strictly type-safe code, for example by ensuring you always check when accessing values that may be undefined.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	let owner = getRouterParam(event, 'owner')
	let repo = getRouterParam(event, 'repo')
	const owner = getRouterParam(event, 'owner')
	const repo = getRouterParam(event, 'repo')
	if (!owner || !repo) {
	return { stars: 0, forks: 0 }
	}

[trueberryless]

LGTM 🎉

Nice refactor. I think the one Rabbit comment can just be resolved 👍