One click turns page text into ranked matches
JavRanking Extension reads the visible text of the active top-level page after you click its toolbar button. It recognizes supported catalog-code shapes, matches them against JavRanking's published index, and opens a side panel with covers, titles, ranking appearances, and detail links. The repository's primary README is written in Simplified Chinese, while README.en.md gives English installation and privacy instructions. This is a narrow browsing companion, not a general video database or player.
The design makes the boundary unusually concrete. A scan is capped at 2 MiB of rendered text and 500 unique candidates, with each candidate limited to 64 characters. It excludes form values, browser pages, cross-origin frames, closed shadow roots, images that would need OCR, and unrendered virtual content. A broad pattern can suggest a code, but only an entry in the JavRanking index becomes a confirmed result. That restraint should reduce strange matches on ordinary pages.
The privacy promise depends on broad page access
Version 1.1.0 asks for activeTab, scripting, sidePanel, and tabs, plus host access to JavRanking, its API, and *://*/*. The last permission looks broad because the tool must inspect whichever site you are viewing. The stated behavior is narrower: it runs after a toolbar click, reads the bound tab's top-level document, and does not send page URLs, page text, DOM content, candidates, or browsing history.
Cloud marking changes the data flow. Want, watched, and dropped states can sync through a Chong Code to api.javranking.cc; the v1.1.0 release reduced the upload debounce from 1,500 ms to 300 ms and added a 30-second conflict buffer. Page-derived text is still supposed to stay local. A competent buyer should inspect the manifest and network calls because the browser permission is broader than the product promise, and JavRanking operates both the lookup data and sync endpoint.
What happened when we ran it
Our sandbox installed commit 206ec97 in 17 seconds. Npm added 176 packages, and the installed tree occupied 149 MB in an unprivileged Node 22 container with 3 CPUs and 8 GB of RAM. The repository itself had 49 files, about 5,360 source lines, and a 1.1 MB checkout. Installation completed without secrets or a privileged browser environment, and npm audit reported 0 known vulnerabilities.
The build finished in 12 seconds. Vitest then completed in 8 seconds with 55 passed and 0 failed tests. One CI workflow and a tests directory are present, while no Dockerfile exists. Those results cover the source build and test suite only. We did not install the release into a graphical browser, scan live adult sites, measure lookup speed, or verify the contents of the remote JavRanking index.
A green build still leaves manual browser work
Chrome and Edge do not get a store button. The documented route is to download the Chromium ZIP, extract it into a folder you will keep, enable Developer mode, and choose Load unpacked. Updates repeat that process, although the extension checks GitHub Releases and displays a notice when a newer version exists. In issue 5, the maintainer answered that the extension would not pass store review and should remain locally installed. That is a meaningful adoption limit, not a cosmetic setup complaint.
Firefox is in a better state than the README says. Release v1.1.0 includes a signed XPI, and the maintainer closed issue 6 after posting that the signed file was available. Yet both the Chinese and English README still say persistent Firefox installation is unavailable. The artifact resolves the practical problem, but the stale instruction costs confidence. For Chromium users, there is no similar escape from manual update handling.
The service recovered quickly, but the history is short
The repository was created on September 7, 2026, reached v1.1.0 on September 19, and was pushed again on September 30. GitHub showed 831 stars and 0 open issues and pull requests on October 1. Closed issue 4 records a real outage: the old javranking.top index host stopped resolving, and v1.0.1 moved the extension to javranking.cc three days after the report. That response was fast, though it also showed how one domain failure can empty the panel.
JavRanking Extension earns a trial if its exact loop is familiar: you see many codes, want ranking context without changing tabs, and already trust JavRanking with synced marks. The 55 clean tests and recent fixes make source inspection easier. The decision turns on distribution and dependence. You must maintain an unpacked Chromium install, accept broad page access, and rely on a young project whose useful results come from one external catalog.