Scan failed for Campaign Swarm, please re-run (cursor.directory/plugins/campaign-swarm)

Open
#534 1 comment 0 reactions 0 assignees View on GitHub

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.

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: error
  • scan_verdict: null
  • scan_run_id: null
  • flag_reasons: []
  • flag_summary: Cursor SDK startup failed: Invalid User API Key
  • last_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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cursor/community-plugins

All issues in cursor/community-plugins

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.