Catalog methodology and evidence

Updated September 30, 2026

Start with an identifiable source

A template links to its source repository and credits the repository owner. Descriptions summarize recorded README and project metadata. A source link lets you inspect the current project; it does not imply that its author reviewed our summary.

Keep license evidence distinct

A platform license label, a retrieved license file and a file compared with standard text represent different levels of evidence. The detail page displays the recorded method and source where available. Check the linked license and asset notices before use; fonts, photos, services and dependencies may have separate terms. Unknown conditions remain unresolved.

Separate file inspection from execution

A repository file check records the retrieval date, source URLs and declared dependency ranges. It does not mean dependencies were installed, a build succeeded or security was audited. A preview is evidence of appearance; it does not establish authentication, payment processing or form delivery.

Label drafting, translation and review

AI assists with descriptions and translations. Detail pages distinguish recorded human approval, automated publication checks and historical entries without a review record. Automated checks are not a named human endorsement. An English detail page is listed only when the required localized record is available.

Classify by framework and purpose

Framework families can overlap: Gatsby and Next.js use React, while Nuxt uses Vue. Category pages prioritize the named primary framework and keep the actual framework label visible. Purpose tags describe recorded use cases, not proof that every advertised feature works.

Recheck before adoption

Repositories and demos can change after collection. Compare the linked source, file-check date and your intended environment. Record a concrete mismatch with its page URL and supporting source through the correction page.