Scan failed for doorfarer, please re-run (cursor.directory/plugins/doorfarer)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 22/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- tooling
Research direction
Read the related issue #414 and investigate the directory team's process for rerunning failed plugin scans. Confirm whether the scanner outage is still affecting this submission, then rerun the scan for the doorfarer listing and publish it if it passes. Done when the scan result is resolved and the listing's directory visibility matches that result.
Written by the indexing model from the issue text.
Description
Hi,
Could an admin please re-run the security scan for our Cursor Directory listing and publish it if it is safe?
- Listing: https://cursor.directory/plugins/doorfarer
- Repo: https://github.com/3nterTheV0id/doorfarer
- MCP server: https://doorfarer.com/mcp (public, no sign-in)
We published it from GitHub on 2 November 2026. The page showed "Scan failed. An admin will re-run it shortly" and "This plugin is unpublished and hidden from the directory." On 3 November we saved the plugin unchanged (Update Plugin) and clicked Submit for verification. The plugin page still loads, but a directory search for "doorfarer" still returns "No plugins found."
This looks like the same scanner outage described in https://github.com/cursor/community-plugins/issues/414, where a Cursor teammate confirmed that scans fail before they read the submission because the scanner's own API key is rejected, and that only the directory team can re-run a scan that ended in an error. There is no existing issue for doorfarer.
Happy to provide anything else you need.
Thanks,
Christopher Bauer
[email protected]
- 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 ·