Transparent methodology
CordisPlugin turns public GitHub repository data into a searchable directory. Here is exactly where listings come from, what we check, what we do not verify, and how to evaluate a plugin before installation.
Current directory snapshot
1,000repositories indexedDiscovery pipeline
Pages are generated from a bounded, versioned snapshot instead of making every visitor request depend on GitHub availability.
Query public, non-archived repositories carrying the dsh-plugin topic.
Read limited public repository fields, documentation signals, release data, and activity metrics.
Use repository IDs as identity, create stable slugs, and normalize plugin types and topics.
Apply explicit listing rules, remove invalid entries, and preserve links to upstream evidence.
Write a versioned snapshot and server-render list and detail pages from one data contract.
Run ingestion again, record the successful sync time, and update changed evidence.
Listing boundaries
A directory entry is a discovery aid, not certification. This matters when third-party code can access files, commands, credentials, tools, or networks.
Evidence guide
Signals describe evidence found in one snapshot. They should never be interpreted more broadly than their definition.
The repository carried the dsh-plugin topic when synchronized.
Author, compatibility, or security was verified.
Named public GitHub fields were retrieved and parsed.
The code or dependency tree received an audit.
An installation reference was detected upstream.
The command was executed, tested, or remains current.
A person reviewed the listing and available evidence.
The plugin is certified, vulnerability-free, or endorsed.
Before installation
Treat every third-party plugin as code you are choosing to trust. Start with the upstream repository, not the directory summary.
Confirm capability, install path, configuration, and uninstall steps.
Check filesystem, network, credentials, native commands, lifecycle scripts, and tool permissions.
Review commits, releases, issues, license, ownership, and dependency health.
Prefer a release or commit and test unfamiliar code in a disposable environment.
Check resulting files and behavior; remove the plugin if reality differs from documentation.
Data freshness
GitHub remains authoritative whenever a directory summary differs from the current repository. Counts and metadata reflect the last successful import, not a live security check.
GitHub search reached the configured result limit, so this directory may not represent every repository carrying the topic.
Explore all pluginsFrequently asked questions
Listings use public repositories discovered through GitHub’s dsh-plugin topic and stored in a versioned local snapshot.
No. Listing is not a security audit, compatibility test, certification, or endorsement.
No. The site displays evidence and copyable starting commands but does not run plugin code on your device.
A maintainer may update, rename, archive, transfer, or delete a repository after the last sync.
Use the footer contact details and include the plugin page, upstream repository, and field requiring correction.