cursor / cursor/community-plugins
Admin clear: stale repository_clone_failed on yieldhuntereth-yieldsentineleth (Source fixed to yieldhunter-connect)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4k
- Forks
- 671
- Avg merge
- 3h 42m
- Merged PRs (30d)
- 1
Description
Request
Please clear / re-scan the Cursor Directory listing after a Source URL fix. Security agent still shows a stale repository_clone_failed against a repo that never existed.
Listing
- Directory URL: https://cursor.directory/plugins/yieldhuntereth-yieldsentineleth
- Title: yieldhunter.eth + yieldsentinel.eth
- Status: Flagged by the security agent; unpublished/hidden pending manual review
What went wrong
Initial submit used a bad Source URL:
- ❌
https://github.com/agentsherpa/yieldhunter(404 — repo does not exist)
We edited the listing and set Source to the correct public repo:
- ✅
https://github.com/agentsherpa/yieldhunter-connect(public;git ls-remoteworks; containsplugin.json+mcp.json+ MIT)
After edit+resubmit, the security banner still cites the old agentsherpa/yieldhunter 404 and keeps the listing unpublished.
Ask
Please clear the stale flag / re-run the security scan against agentsherpa/yieldhunter-connect so the listing can become publishable (or tell us if another action is required).
Notes
- No payment involved
- Thin public connect repo only (intentional); private agent code stays private
- Sibling MCP: https://github.com/agentsherpa/yieldsentinel-connect (not the Directory Source)
Thanks!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the listing's stored Source URL and the security-agent result for cursor.directory/plugins/yieldhuntereth-yieldsentineleth. Re-run the scan against agentsherpa/yieldhunter-connect and verify that the stale repository_clone_failed banner is cleared and the listing can become publishable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github, typescript
- Domain
- security, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100