SteadWeave Companion
| 开发者 | drepar |
|---|---|
| 更新时间 | 2026年8月26日 00:37 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
Free Forever: 1 website, complete monitoring
SteadWeave Free includes complete monitoring for one website, free forever. There is no trial period and no expiration.
SteadWeave Companion is the complete WordPress plugin, not a separate “Lite” or feature-locked edition. Paid plans are available when you need to monitor more websites.
SteadWeave Companion is the lightweight WordPress-side connector for the SteadWeave external monitoring service.
The Companion does not perform the central monitoring workload locally. After a WordPress administrator explicitly starts setup and confirms the external-service disclosure, the plugin connects the site to SteadWeave. After pairing, authenticated technical heartbeats let the service evaluate WordPress health, software versions, update availability and other website-assurance signals.
The PHP, JavaScript, CSS, translations, documentation and bundled image assets distributed in this WordPress.org plugin package are licensed under GPLv2 or later. The SteadWeave name and source-identifying marks may also be protected by applicable trademark law; those trademark rights are separate from, and do not restrict, the GPL license granted for the copies of the bundled assets distributed with this plugin. See
ASSET-LICENSE.txt and LICENSE.txt.
SteadWeave is a separate SaaS service. Service plans may differ by the number of websites that can be managed. The Companion does not hide premium PHP code or unlock local plugin functionality with a license key.
What the Companion does
- Provides a request-first secure pairing flow.
- Creates a cryptographic installation identity used to verify control of the WordPress installation.
- Stores issued access credentials locally using authenticated encryption when supported by the server.
- Sends authenticated technical heartbeats only after pairing.
- Advertises locally available Smart Fix capabilities to the paired service.
- Receives bounded, authenticated Smart Fix commands only after pairing and only after an authorized SteadWeave account user explicitly requests Assisted Remediation.
- Can update supported SEO metadata through Yoast SEO, Rank Math, AIOSEO or SEOPress when one supported provider is detected unambiguously.
- Can replace exact verified HTTP hyperlink references in published WordPress post content without requiring an SEO plugin.
- Verifies Smart Fix targets and current values, reports structured results, and supports bounded preflight and rollback safeguards.
- Reports WordPress/PHP versions, plugin/theme inventory and update state, site URLs, limited server context and WordPress cron state used by the monitoring service.
- Receives SteadWeave branding and the customer dashboard URL as part of authenticated service responses.
- Provides connection diagnostics and an administrator-only recovery path.
- Stops scheduled authenticated telemetry when pairing is reset or the plugin is deactivated.
- Integrates with WordPress privacy-policy, personal-data export and personal-data erasure tools for the locally stored enrollment email.
安装:
- Install and activate SteadWeave Companion.
- Open SteadWeave in the WordPress administration menu.
- Review the external-service disclosure and linked Privacy Notice and Terms of Service.
- Enter the email address to use for setup notifications.
- Explicitly confirm the external-service connection.
- Select Start secure setup.
- Complete the guided setup on app.steadweave.com.
- Return to WordPress and verify that the connection status becomes Connected.
屏幕截图:
常见问题:
Does the plugin send data immediately after activation?
No. Activation creates local cryptographic installation material but does not contact SteadWeave. Scheduled authenticated heartbeats are enabled only after a valid pairing is completed. The first enrollment request is sent only after an administrator confirms the external-service disclosure.
Which server does the production plugin connect to?
The official production endpoint is https://app.steadweave.com/. A production installation cannot redirect normal SteadWeave traffic to an arbitrary server through the standard plugin interface.
Why does the plugin expose REST enrollment endpoints?
They are callback endpoints used by SteadWeave to verify control of the WordPress installation and complete pairing before normal service credentials exist. The proof endpoint is available only during a short enrollment window. Both callback paths are rate-limited, and enrollment completion is cryptographically authenticated in the route permission callback before the write callback is allowed to run.
Can SteadWeave modify WordPress content?
Only through the bounded Assisted Remediation features described above, after an authorized SteadWeave account user explicitly requests a supported Smart Fix. The Companion does not accept arbitrary code or arbitrary content-write commands.
Is SteadWeave Companion a paid plugin?
No. SteadWeave Companion is the complete GPLv2-or-later WordPress plugin and contains no hidden premium PHP functionality or separate Lite edition. SteadWeave Free provides complete monitoring for one website, free forever, with no trial period or expiration. Paid service plans are available when you need to monitor more websites.
What happens if I disconnect the Companion?
Local pairing credentials, synchronized connection state and the local Smart Fix anti-replay ledger are removed, and scheduled heartbeats are stopped. Data already held by the SteadWeave service is handled according to the service Privacy Notice and retention settings.
Where can I find documentation?
Documentation is published at https://docs.steadweave.com/.
更新日志:
1.0.9
- Preserve the real upstream HTTP status when a successful SteadWeave response is later rejected by local pairing-response validation.
- Add safe enrollment diagnostics that identify the response-validation phase and a non-secret reason code, including central URL mismatches, without exposing credentials or pairing tokens.
- Clear the new diagnostic metadata on successful communication, pairing reset and uninstall while keeping production central-server pinning unchanged.
- Fix approved-but-unpaired enrollment recovery: Refresh setup status can securely request fresh pairing credentials when central delivery was not confirmed, verify them before local storage, and finish the authenticated connection without manual credential entry.
- Keep the 1.0.7 WordPress.org Free Forever messaging, screenshots, Smart Fix retention disclosure, response-size hardening and reset cleanup unchanged.
- Make the Companion UI distinguish approval from an actually completed pairing, so an APPROVED request is no longer shown as Awaiting approval or told to repeat the central onboarding wizard.
- Make the Free Forever offer prominent in the WordPress.org listing: complete SteadWeave monitoring for one website, with no trial period or expiration.
- Clarify that SteadWeave Companion is the complete plugin, not a separate Lite or feature-locked edition.
- Refresh the WordPress.org banner message to highlight the one-site Free Forever offer.
- No functional behavior changes from 1.0.6.
- Add official WordPress.org screenshots and listing captions for the secure setup and Assurance dashboard flows.
- Refresh public release metadata for the WordPress.org 1.0.6 tag.
- No functional behavior changes from 1.0.5.
- Fix the WordPress admin menu icon regression by using a dedicated 20x20-pixel bundled icon instead of the full-size branding artwork.
- Separate the admin-menu icon accessor from the dashboard/favicon branding icon so future branding changes cannot alter the menu icon dimensions.
- Synchronize the Italian translation catalog with the final 1.0.5 source strings and translator context.
- Clear the local Smart Fix anti-replay ledger and remediation diagnostics when pairing is reset, and document its bounded seven-day retention.
- Verify secure enrollment-secret persistence before using newly generated enrollment material.
- Bound SteadWeave HTTP response sizes and make loopback-host handling consistent across enrollment, heartbeat, remediation reporting and branding validation.
- Add the required translator context for the external-service URL placeholders in the WordPress privacy-policy text.
- Removed pre-public-release storage, cryptography and REST compatibility shims so the WordPress.org package uses only the canonical SteadWeave Companion identifiers and REST namespace.
- Clarified that all bundled plugin assets, including the shipped logo and icon copies, are GPLv2 or later while trademark rights remain separate.
- Scoped Companion branding, palette styling and favicon changes to the SteadWeave admin screen; the WordPress admin menu uses the bundled local icon.
- Removed synchronous branding HTTP requests from WordPress administration requests. Branding is synchronized only through authenticated service responses such as enrollment and heartbeat traffic.
- Moved enrollment-completion payload-size and HMAC authentication checks into the REST
permission_callbackbefore the write callback executes. - Expanded the external-service and WordPress privacy disclosures to document all supported Smart Fix operations and remediation-result data.
- Clarified that Smart Fix does not download arbitrary executable code, install extensions or provide a general-purpose remote code execution mechanism.
- Removed per-request cron schedule repair from
init; schedules are managed at activation, successful pairing, reset and deactivation boundaries. - Reformatted review-sensitive PHP for human readability and cleaned the public changelog to published 1.x releases only.
- Updated the WordPress.org
Tested up todeclaration to WordPress 7.1. - Prefixed the uninstall loop variable to satisfy WordPress global naming conventions.
- Replaced the dynamic filter-name invocation in product URL resolution with explicit prefixed filter hooks.
- Aligned the gettext text domain with the
steadweave-companionWordPress.org slug. - Replaced short global identifiers with collision-safe SteadWeave Companion namespaces, constants, options and hooks.
- Replaced directly emitted admin CSS with WordPress enqueue APIs and context-appropriate output escaping.
- Initial public SteadWeave Companion release.