Title: Rooted Dev Studio Security Toolkit Author: bigdawgdad2185 Published: Ògún 29, 2026 Last modified: Ògún 29, 2026 --- Ṣàwárí àwọn plugin ![](https://ps.w.org/rooted-dev-studio-security-toolkit/assets/icon-256x256.png? rev=3671852) # Rooted Dev Studio Security Toolkit Láti ọwọ́ [bigdawgdad2185](https://profiles.wordpress.org/bigdawgdad2185/) [Ṣe ìgbàsílẹ̀](https://downloads.wordpress.org/plugin/rooted-dev-studio-security-toolkit.0.2.1.zip) * [Àwọn àlàyé](https://yor.wordpress.org/plugins/rooted-dev-studio-security-toolkit/#description) * [Àwọn àgbéyẹ̀wò](https://yor.wordpress.org/plugins/rooted-dev-studio-security-toolkit/#reviews) * [Ìgbéwọlẹ̀](https://yor.wordpress.org/plugins/rooted-dev-studio-security-toolkit/#installation) * [Ìdàgbàsókè](https://yor.wordpress.org/plugins/rooted-dev-studio-security-toolkit/#developers) [Ìrànlọ́wọ́](https://wordpress.org/support/plugin/rooted-dev-studio-security-toolkit/) ## Àpèjúwe Rooted Dev Studio Security Toolkit provides a transparent baseline for protecting a WordPress website without hiding important behavior behind vague scores or destructive automatic fixes. Features include: * Configurable failed-login limiting with short, per-login-and-IP temporary lockouts. * Administrator controls for reviewing and clearing active Rooted Dev Studio Security Toolkit lockouts. * Time-based two-factor authentication with single-use recovery codes. * A local Security Timeline for important authentication, administration, hardening, and file events. * Hashed origin records without storing raw IP addresses in security events. * Baseline browser security headers. * Reversible theme and plugin editor protection. * Optional XML-RPC authentication restriction. * Optional public REST user endpoint restriction. * Security configuration checks for HTTPS, updates, debug display, administrator access, WordPress salts, and PHP. * Read-only file fingerprinting with expected and unexplained change review. * A bounded, manual suspicious-code scan for selected high-risk PHP patterns. * Email alerts for important software and administrator changes and repeated-login lockouts. * Local retention controls and automatic cleanup. Rooted Dev Studio Security Toolkit does not transmit site data to Rooted Dev Studio or any third party. It does not execute, edit, quarantine, restore, or delete scanned files. A clean scan is not a guarantee that a website is free of malicious code. Rooted Dev Studio Security Toolkit does not replace secure hosting, backups, software updates, or professional incident response. ## Ìgbéwọlẹ̀ 1. Upload the `rooted-security` folder to `/wp-content/plugins/`, or install the ZIP through Plugins > Add New > Upload Plugin. 2. Activate Rooted Dev Studio Security Toolkit. 3. Open Rooted Dev Studio Security Toolkit > Dashboard. 4. Review Rooted Dev Studio Security Toolkit > Settings before enabling compatibility- sensitive options. 5. Configure two-factor authentication from each administratorÌtumọ̀ Yorùbá: ’s WordPress profile and store recovery codes securely. 6. Create a file-monitor baseline only after confirming the website is in a known- good state. ## FAQ ### Does Rooted Dev Studio Security Toolkit send my site data anywhere? No. Rooted Dev Studio Security Toolkit Free has no telemetry, remote API, account requirement, or external service connection. ### Does the suspicious-code scan prove my website is clean? No. The bounded, read-only scanner looks for selected high-risk PHP patterns in active themes and plugins. Findings require review, and a clean result cannot detect every malware family or hidden compromise. ### Why are XML-RPC and REST user restrictions disabled by default? Those options can affect mobile apps, publishing tools, and integrations. Rooted Dev Studio Security Toolkit keeps compatibility-sensitive controls opt-in. ### Are IP addresses stored? Raw IP addresses are not written to the activity table. Rooted Dev Studio Security Toolkit stores a keyed hash so repeated events can be correlated without retaining the original address. ### Can login protection lock every visitor out of an account? No. Temporary lockouts are tied to the matching login value and the server-observed IP address. Password-reset access remains available, active administrators can clear Rooted Dev Studio Security Toolkit lockouts, and a file-access recovery constant is documented on the Login Protection screen. ### Does Rooted Dev Studio Security Toolkit automatically change or delete suspicious files? No. File monitoring and suspicious-code scanning are review tools. Rooted Dev Studio Security Toolkit does not automatically modify, quarantine, restore, or delete files. ## Àwọn àgbéyẹ̀wò Kò sí àwọn àgbéyẹ̀wò fún plugin yìí. ## Àwọn Olùkópa & Olùgbéejáde “Rooted Dev Studio Security Toolkit” jẹ́ ètò ìṣàmúlò orísun ṣíṣí sílẹ̀. Àwọn ènìyàn wọ̀nyí ti ṣe ìkópa sí plugin yìí. Àwọn Olùkópa * [ bigdawgdad2185 ](https://profiles.wordpress.org/bigdawgdad2185/) [Túmọ̀ “Rooted Dev Studio Security Toolkit” sí èdè rẹ.](https://translate.wordpress.org/projects/wp-plugins/rooted-dev-studio-security-toolkit) ### Ṣe o nífẹ̀ẹ́ sí ìdàgbàsókè? [Ṣàwárí koodu](https://plugins.trac.wordpress.org/browser/rooted-dev-studio-security-toolkit/), ṣàyẹ̀wò [ibi ìpamọ́ SVN](https://plugins.svn.wordpress.org/rooted-dev-studio-security-toolkit/), tàbí ṣe àgbékalẹ̀ sí [àkọsílẹ̀ ìdàgbàsókè](https://plugins.trac.wordpress.org/log/rooted-dev-studio-security-toolkit/) nípasẹ̀ [RSS](https://plugins.trac.wordpress.org/log/rooted-dev-studio-security-toolkit/?limit=100&mode=stop_on_copy&format=rss). ## Àkọsílẹ̀ àwọn àyípadà #### 0.2.1 * Renamed the plugin for a distinctive WordPress.org identity. #### 0.2.0 * Added local two-factor authentication and single-use recovery codes. * Added the local Security Timeline and dashboard summary. * Added reversible hardening controls and review history. * Added read-only file fingerprinting and expected-change review. * Added a bounded manual suspicious-code scanner with PHP comment filtering. * Added windowed login limiting, administrator lockout recovery, timeline events, and anti-flood email alerts. * Expanded privacy, safety-scope, and uninstall cleanup documentation. * Addressed WordPress Plugin Check translation, request-validation, package, and database-query findings. * Corrected translator-comment placement in administrative templates. * Normalized production source-file line endings. ## Àkójọpọ̀ Meta * Ẹ̀yà **0.2.1** * Ìgbàgbọ́hùn tó kẹ́yìn **ọ̀sẹ̀ 3 sẹ́yìn** * Àwọn ìgbéwọlẹ̀ tó ṣiṣẹ́ **Tó kéré sí 10** * Ẹ̀yà WordPress ** 6.5 tàbí ju bẹ́ẹ̀ lọ ** * Dánwò dé **7.1.1** * Ẹ̀yà PHP ** 7.4 tàbí ju bẹ́ẹ̀ lọ ** * Èdè * [English (US)](https://wordpress.org/plugins/rooted-dev-studio-security-toolkit/) * Àwọn àmì * [Activity Log](https://yor.wordpress.org/plugins/tags/activity-log/)[hardening](https://yor.wordpress.org/plugins/tags/hardening/) [login security](https://yor.wordpress.org/plugins/tags/login-security/)[security](https://yor.wordpress.org/plugins/tags/security/) [Security Headers](https://yor.wordpress.org/plugins/tags/security-headers/) * [Ìwòye Tó Péye](https://yor.wordpress.org/plugins/rooted-dev-studio-security-toolkit/advanced/) ## Àwọn ìbò Kò sí ìwádìí tí a tíì fi ránṣẹ́. [Your review](https://wordpress.org/support/plugin/rooted-dev-studio-security-toolkit/reviews/#new-post) [Wo gbogbo àwọn àgbéyẹ̀wò](https://wordpress.org/support/plugin/rooted-dev-studio-security-toolkit/reviews/) ## Àwọn Olùkópa * [ bigdawgdad2185 ](https://profiles.wordpress.org/bigdawgdad2185/) ## Ìrànlọ́wọ́ Nǹkan wà tí o fẹ́ sọ? Ṣé o nílò ìrànlọ́wọ́? [Wo àpéjọ ìrànlọ́wọ́](https://wordpress.org/support/plugin/rooted-dev-studio-security-toolkit/)