feat(enrichment): hardcoded-URL / raw-endpoint heuristic analyzer

[bohdansolovie]

Summary

Fixes #2027

• Add HardcodedUrlFinding and a local hardcodedUrl analyzer for absolute HTTP(S) URLs and raw IP:port endpoints on added non-test, non-config source lines
• Allowlist localhost, 127.0.0.1, and example.com; skip comment/import lines; report redacted hosts only (never full paths or queries)
• Register the analyzer in the REES registry with render/docs/metadata
• Add review-enrichment/test/hardcoded-url.test.ts covering flagged URLs, allowlisted hosts, test/config skip, cap, and brief rendering

Test plan

• cd review-enrichment && npm run build && npm run metadata && node --test test/hardcoded-url.test.ts test/analyzer-registry.test.ts
• CI validate-code

Made with Cursor

[superagent-security]

Superagent didn't find any vulnerabilities or security issues in this PR.

[loopover-orb]

Warning

🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨

⏸️ Gittensory review result - manual review recommended

_{Review updated: 2026-07-05 08:55:55 UTC}

9 files · no blockers · readiness 62/100 · CI green · clean

⏸️ Suggested Action - Manual Review

Nits — 1 non-blocking

• Readiness score is below the configured threshold — Use the readiness panel as advisory maintainer context; the score does not block this PR.

Signal	Result	Evidence
Code review	✅ No blockers	No AI review summary
Linked issue	✅ Linked	#2027
Related work	⚠️ 3 scoped overlaps	Top overlaps are listed below; lower-confidence bulk is hidden.
Change scope	❌ 8/20	High review scope from cached public metadata (1 linked issue).
Validation posture	❌ 5/25	Preflight is holding this PR: the review lane is unavailable, so it is not ready for automated review.
Contributor workload	✅ 10/10	Author activity: 287 registered-repo PR(s), 177 merged, 9 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	bohdansolovie; Gittensor profile; 287 PR(s), 9 issue(s).
Gate result	✅ Passing	No configured blocker found.

Review context

• Author: bohdansolovie
• Role context: outside_contributor
• Public audience mode: oss maintainer
• Lane context: Repository registration is not available in the local Gittensory cache.
• Public profile languages: not available
• Official Gittensor activity: 287 PR(s), 9 issue(s).
• Related work: Titles/paths share 7 meaningful terms. (issue #2029, issue #2027)
• Related work: Titles/paths share 7 meaningful terms. (issue #2019, issue #2027)
• Related work: Titles/paths share 6 meaningful terms. (issue #2026, issue #2027)

Contributor next steps

• Review top overlaps.
• Add a concise scope and risk note.
• Await review-lane availability.
• Refresh registry data or choose a registered active repo.
• Check active issues and PRs before submitting.

Signal definitions

• Related work = same linked issue, overlapping active PRs, or title/path similarity.
• Change scope = cached public metadata such as size labels, draft state, and review-burden hints.
• Validation posture = whether the PR provides enough public validation/test evidence for maintainer review.
• Contributor workload = public contributor activity and cleanup pressure, not a repo-wide quality failure.
• Contributor context = public GitHub/Gittensor identity context; non-Gittensor status is not a blocker.

_{🟩 Safe / merged · 🟦 Advisory · 🟨 Held for review · 🟥 Blocked / closed}

---

💰 Earn for open-source contributions like this. Gittensor lets GitHub contributors earn for the work they already do — register to start earning →.

Checked by Gittensory, a quiet PR intelligence layer for OSS maintainers.

• Re-run Gittensory review

[loopover-orb]

Gittensory approves — the gate is satisfied and CI is green.