fix: enforce tracked-repo allowlist on remaining repos API routes#157
fix: enforce tracked-repo allowlist on remaining repos API routes#157glorydavid03023 wants to merge 1 commit into
Conversation
Add assertTrackedRepo to list/meta, badges, validations, author feeds, and related-prs index handlers so untracked owner/name pairs cannot read hub cache data. Co-authored-by: Cursor <cursoragent@cursor.com>
|
Warning Review limit reached
More reviews will be available in 50 minutes and 45 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (9)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Thanks for contributing. Gittensor policy allows at most 2 open pull requests per contributor at a time. @glorydavid03023 currently has 3 open pull requests, and this is open PR #3. Please finish or close one of the older open pull requests before opening another. |
Summary
assertTrackedRepoon repo-scoped list and metadata API routes that were still missing the allowlist check after fix: reject requests for repos not in the tracked allowlist #142.Test plan
pnpm run lintandpnpm buildGET /api/repos/<tracked-owner>/<tracked-repo>/issuesreturns data for a configured repoGET /api/repos/random-owner/random-repo/issuesreturns 404