Just a silly project to see if I can create WordPress plug-ins. It displays a list of GitHub repositories or the README.md of a single repository.
Repository metrics are context, not quality scores. Active installations measure adoption and can strongly reflect a plugin’s age and historical popularity. Ratings, recent updates and “Tested up to” metadata also do not guarantee modern code, error-free operation, security, feature completeness or suitability for a particular site. Why active installs don’t tell the whole story →
WP PlugIndex currently records GitHub Repositories version 1.0.0 as active, updated 7y ago and tested up to WordPress 5.1.
You define the plug-in with the shortcode list-github-repositories. Don’t forget to define the user whose plug-ins you want to display, else you’ll get mine.
Afterwards you get a nice list with your repositories.
Similarly you can use a shortcode like [show-github-repository user="slothsoft" repository="wordpress-github-repositories"] to show a single repository’s HTML. GitHub parses the HTML itself, so you don’t need to fear unsupported markup.
Not yet marked as tested with WordPress 7.1. WordPress.org currently lists Tested up to 5.1.
“Tested up to” is directory metadata supplied by the plugin author. WP PlugIndex does not turn an older declaration into a claim that the plugin is incompatible.
No tracked version or compatibility changes have been recorded by WP PlugIndex yet.
WP PlugIndex tracks public WordPress.org directory metadata and records selected version, compatibility and availability changes as they are detected.
