JSM Force HTTP to HTTPS / SSL

Quick answers

Is JSM Force HTTP to HTTPS / SSL still maintained?

Yes. Last release 29 Oct 2026, 0 releases in the last 24 months. 29 Oct 2026 · wordpress.org

Who owns JSM Force HTTP to HTTPS / SSL, and has it changed hands?

No change recorded. Main committer jsmoriss since Jan 2017. 3 Nov 2026 · SVN log

Was JSM Force HTTP to HTTPS / SSL removed from wordpress.org?

No. Listed on wordpress.org as of 3 Nov 2026. 3 Nov 2026 · wordpress.org

Is JSM Force HTTP to HTTPS / SSL safe?

No known vulnerabilities on record. 3 Nov 2026 · Wordfence Intelligence

Is the latest JSM Force HTTP to HTTPS / SSL update safe to install?

No ownership change before 3.5.0. No one-star spike after it. 30 Sep 2024 · Release history

Active signals

Facts we detected, with links to the source.

No open risk signals. Signals appear here when we detect an ownership change, closure, vulnerability or decline.

Ownership timeline

Who commits to the plugin's code on wordpress.org, over time.

1 committer recorded. No ownership change since 2017.

Security record

No published vulnerabilities on record for this plugin.

Sources: Wordfence Intelligence, CISA Known Exploited Vulnerabilities, readme changelogs.

Healthier alternatives

Same job, rated Healthy, higher Canary Score and at least 10,000 installs. Never sponsored.

No healthier plugin in the same category yet.

Facts

Other plugins by this author: JSM Show Post Metadata, WPSSO Core - Complete Schema Markup and Meta Tags, JSM Show User Metadata, JSM Non-Breaking Space (nbsp) for French Content, WPSSO Tune WP Image Editors, JSM Show Term Metadata, JSM Show Order Metadata for WooCommerce HPOS, WPSSO Schema Product Metadata for WooCommerce, WPSSO WP Sitemaps XML with News, Image, and Video Sitemap, WPSSO Schema Organization and Place Manager, JSM file_get_contents() Shortcode, WPSSO Schema Breadcrumbs Markup

Questions