cursor / cursor/community-plugins
Scan failed on 18 HasData plugins submitted 2026-09-14, identical repos passed on 09-11; please re-run
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4k
- Forks
- 671
- Avg merge
- 3h 42m
- Merged PRs (30d)
- 1
Description
18 plugins stuck on "Scan failed. An admin will re-run it shortly."
All 18 were submitted on 2026-09-14 through Auto (GitHub) and have shown Scan failed. An admin will re-run it shortly. This plugin is unpublished and hidden from the directory. since then. Edit → Update Plugin does not re-trigger the scan, and there is no Rescan control on the owner side.
The repositories are public, cloneable, MIT-licensed, and identical in layout to six sibling listings from the same account that passed the scan instantly on 2026-09-11 and are live today (airbnb-mcp-server, amazon-mcp-server, bing-mcp-server, bookingcom-mcp-server, duckduckgo-mcp-server, zillow-mcp). Each repo has plugin.json and mcp.json at the root (Agent Plugins 1.0.0), one streamable-http server with an x-api-key header placeholder, no credentials committed.
Ask
Please re-run the security scan on these 18 listings. If something in the repositories is the cause, a pointer to the failing check would let us fix it ourselves. Owner account: sergey-ermakovich (sergey@hasdata.com).
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
Compare the root plugin.json and mcp.json files in the 18 linked repositories with the six sibling listings that passed on 2026-09-11. Start by identifying the scan failure or re-run entry point in the community-plugins project; done means the affected scans complete successfully and the listings are no longer hidden, or the failing check is identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, typescript
- Domain
- devtools, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100