cursor / cursor/community-plugins
Two plugins stuck: Scan failed + Verification requested locked (no Rescan)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4k
- Forks
- 671
- Avg merge
- 3h 42m
- Merged PRs (30d)
- 1
Description
Plugins stuck after security scan failure
Both owner listings show Scan failed. An admin will re-run it shortly. and Verification requested is disabled. There is no Rescan control. Publish stays blocked while unpublished/hidden.
Listing 1
- URL: https://cursor.directory/plugins/lawrence-agent-plugins
- Repo: https://github.com/LAHutchins91/lawrence-agent-plugins
- Manifest:
.cursor-plugin/marketplace.json - Notes: Initial scan failed (marketplace.json had illegal
category/keywords; fixed and pushed in4744b36). Owner UI cannot force a new scan against the fixed commit. Edit → Update Plugin appears to re-save stored form payload, not re-import GitHub.
Listing 2
- URL: https://cursor.directory/plugins/paid-apps-security-funnels
- Repo: https://github.com/LAHutchins91/paid-apps-marketplace
- Manifest:
.cursor-plugin/marketplace.json - Notes: Fresh submit after owner
{ "name": "..." }fix (0ef7903). Toast:Verification requested. We'll review it shortly.Scan banner went from Scanning… → Scan failed again. Same locked Verification requested / no Rescan.
What we need
Please admin-rescan both plugin IDs (or clear orphaned scan_status and re-enqueue), then allow Publish once safe.
Happy to provide anything else. 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 with the owner UI flow for the two listings and the stored scan_status associated with their plugin records. Review the fixed .cursor-plugin/marketplace.json manifests and the scan/verification entry points; done means both listings can be rescanned or re-enqueued and can proceed to Publish after a safe scan.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100