Scan failed for doorfarer, please re-run (cursor.directory/plugins/doorfarer)

Open
#522 0 comments 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
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?

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

  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.