Redesign homepage with ranked plugin leaderboard#383
Open
pontusab wants to merge 4 commits into
Open
Conversation
Replaces the Popular / Recently Added / Most Starred grids and the homepage members section with a single ranked, skills.sh-style leaderboard. - New PluginLeaderboard with All Time / Recent / Most Starred tabs, flat borderless rows, and infinite scroll up to the top 500 - Hero search now filters the leaderboard directly via Fuse instead of rendering separate plugin and member result blocks; placeholder scoped to plugins - Hero copy aligned with Cursor's marketplace voice: "Extend Cursor with community plugins" / "Discover and install plugins from N+ developers, ranked by installs" Co-authored-by: Cursor <cursoragent@cursor.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Adds a velocity-based Trending sort to the homepage leaderboard, sourced from a `plugin_install_snapshots` table populated daily via pg_cron and exposed through the `plugin_install_velocity` SQL function. Real velocity ranks first; a synthetic per-month estimate (lifetime / age) ranks the long tail so the list stays populated before snapshots accumulate. Also drops the redundant author label next to each plugin name and tweaks the hero subhead to match the new ranking story. Co-authored-by: Cursor <cursoragent@cursor.com>
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
- Switch runSecurityAgent from the Cursor cloud runtime to local
runtime. Clone the submitted public repo to /tmp via `git clone
--depth=1 --single-branch --filter=blob:limit=10m`, run the agent
against it with `local: { cwd }`, clean up in a finally. The cloud
runtime requires the Cursor GitHub App to be installed on each
scanned repo, which can't work for a public marketplace where
authors submit arbitrary repos we don't own. Clone failures
degrade to a non-fatal manual-review verdict instead of crashing
the workflow.
- Patch @workflow/world@4.1.1 with the upstream Zod 4.4.x fix
(vercel/workflow#1902) so workflow runs can persist state under
our pinned zod@4.4.3. The local storage round-trips through
JSON.stringify (which strips undefined keys), and zod@4.4.x's
strict treatment of z.undefined() then rejects the read. Drop the
patch once a fixed @workflow/world release lands on npm.
- Sync apps/cursor/.env.example to what the code actually reads:
add CURSOR_API_KEY, GITHUB_TOKEN, NEXT_PUBLIC_OPENPANEL_CLIENT_ID;
drop unused MCP_OWNER_ID and NEXT_PUBLIC_APP_URL.
Co-authored-by: Cursor <cursoragent@cursor.com>
The agent's full reasoning (summary + reasons list) was visible to anyone who hit the URL of a hidden plugin directly. Keep that detail for the owner so they know what to fix, but show the public only a one-line "pending manual review" headline that signals the submission is being triaged rather than permanently rejected. Co-authored-by: Cursor <cursoragent@cursor.com>
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using high mode and found 2 potential issues.
There are 3 total unresolved issues (including 1 from previous review).
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 137507b. Configure here.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Replaces the homepage's grid-of-cards layout with a single, ranked, infinite-scrolling leaderboard focused entirely on plugins.
Three sorts, one list:
lifetime × 30 / age) for plugins without snapshot history yetHow Trending stays honest:
install_countintoplugin_install_snapshots, scheduled via Supabasepg_cron(no Vercel cron route, no Node code path)plugin_install_velocity(window_days)SQL function returns 30-day deltas; for plugins younger than the window it returns the full install count (every install happened inside the window by definition)Other UX changes on the page:
revalidatedropped from 24h → 1h so the leaderboard reflects fresh velocity within an hour of each snapshotNote
Medium Risk
Introduces new Supabase tables/functions plus
pg_cronscheduling and changes the plugin security scan to clone repos locally, so failures could affect ranking accuracy, DB operations, or scanning reliability/resource usage.Overview
Redesigns the homepage to center on a single, infinite-scrolling plugin leaderboard with Trending/Top/New tabs, replacing the prior card-grid sections (including member search/sections) and tightening search to plugin-only.
Adds a DB-backed “trending” signal: a new
plugin_install_snapshotstable,snapshot_plugin_installs()dailypg_cronjob, andplugin_install_velocity()RPC consumed via newgetPluginInstallVelocity(); the homepage revalidate window is reduced to 1 hour to reflect updated velocity.Updates plugin scanning to run Cursor’s agent in
localmode by shallow-cloning the GitHub repo into/tmpwith size/time limits and returning a low-severity “manual review required” verdict when cloning fails, and adjusts flagged messaging/details visibility (only shown to owners).Reviewed by Cursor Bugbot for commit 137507b. Bugbot is set up for automated code reviews on this repo. Configure here.