Scan failed for Campaign Swarm, please re-run (cursor.directory/plugins/campaign-swarm)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- devtools
Research direction
The issue reports a failed security scan for the Campaign Swarm listing and asks an admin to rerun it. Start by reading the scan handling entry point and related tests in the repository; neither is named in the issue. Done means rerunning the scan and confirming whether the listing payload needs changes. The report suggests the failure may be in the scanner's Cursor SDK key, so this likely requires maintainer access.
Written by the indexing model from the issue text.
Description
Hello Cursor Directory team,
Please re-run the security scan for Campaign Swarm.
- Listing: https://cursor.directory/plugins/campaign-swarm
- Repository: https://github.com/campaign-swarm/mcp (public, MIT)
- Contact: [email protected]
The listing has shown “Scan failed. An admin will re-run it shortly.” and “This plugin is unpublished and hidden from the directory.” since submission on 2026-11-15. There is no owner-side rescan control.
The current listing record reports:
scan_status:errorscan_verdict:nullscan_run_id:nullflag_reasons:[]flag_summary:Cursor SDK startup failed: Invalid User API Keylast_scanned_at:2026-11-15T06:30:46.109+00:00
We repaired the repo-side payload before the most recent rescan. Root plugin.json and mcp.json validate against Agent Plugins 1.0.0; mcp.json uses streamable-http with the production OAuth URL and no placeholder header. Both files are now on public main (commit 61d3477).
Because scan_run_id and scan_verdict are null, the failure appears to occur before a scan verdict, in the scanner's own Cursor SDK key. Could an admin please re-run the scan and confirm whether any payload change is needed? Thank you.
- Dominant language
- TypeScript
- Stars
- 4k
- Forks
- 671
- Avg merge
- 7m
- Merged PRs (30d)
- 32
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from cursor/community-plugins
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
cursor/community-plugins#583 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 76/100
cursor/community-plugins#578 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
cursor/community-plugins#576 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
cursor/community-plugins#572 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 74/100
cursor/community-plugins#567 · 4 comments ·
Maintainers usually reply within 1 day
All issues in cursor/community-plugins
Similar issues
-
[UI] Guard webApis against undefined window in SSR environmentsPossibly taken @madhavzanwar claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
headroomlabs-ai/headroom#4992 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
paperclipai/paperclip#22575 ·
Maintainers usually reply within 1 day
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 82/100
lingdojo/kana-dojo#34502 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
bug frontend good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
nikhilb2/simple_invoicing#935 ·