AppFinder is a software directory, and it makes money the way directories do: sponsored slots, a category leaderboard ordered by spend, paid launch boosts. It also promises that none of that can touch the organic ranking. The ranked lists come from five inputs, published on the ranking page : community upvotes (40%), visitor ratings (30%), feedback on recommendations (10%), how complete the listing is (15%) and freshness (5%).
A promise like that is easy to break by accident. One helper imported from the billing module into a scoring file, or one join on the orders table "just to show a badge", and the ranking can see money. Code review won't always catch it. So the rule lives in CI, in three layers.
Layer 1: an import ban in ESLint
The code that ranks or recommends lives in a known set of folders: scoring, search and recommendations, the AI advisor and the MCP tools AI assistants call, the crawler, votes, the weekly email and a few more (26 folders today).…