seek://methodology
Methodology
What every label and number on this site means — the trust tiers, the data pipeline, and the honest limits.
Two trust tiers
Directory entries are editor-verified: a human checked the repository, the integration with DSH, and the description before indexing, and re-checks on every verifiedAt bump. This is curation, not certification.
Discover-queue entries are auto-discovered: harvested from the GitHub dsh-plugin topic by stars, never touched by an editor. They are leads, not listings.Discover queue →
Where every number comes from
All statistics — stars, forks, downloads — are build-time snapshots of the GitHub and npm APIs, snapshotted in the repo. A failed fetch keeps the previous value (fail-closed); nothing is ever typed by hand, and an unknown value is null, never zero.
Derived metrics
Weekly deltas on the homepage are the diff between the latest daily snapshot and the closest one at least seven days older — two real readings, never an estimate.
Pack slots fill by rule: grounded picks rank first, then runnable installs, then official, then snapshot stars. The market feed carries installable, active entries only. Badges show the verification month — no daily statistic ever appears in a badge.
What we do not claim
Verified ≠ endorsed
Editor verification checks honesty, not quality or fitness for your use.
Editor-checked ≠ security audit
Nobody here runs sandbox installs or scans dependencies. Treat third-party plugins as third-party code.
Snapshot ≠ live
Numbers drift between rebuilds; each page carries its snapshot date.
Not indexed ≠ nonexistent
The directory is quality-first and the queue is star-ranked — absence from either proves nothing.
Corrections
Wrong number, dead link, mislabeled entry? File an issue or pull request on the site repository — corrections land on the next rebuild.file an issue ↗