Skip to main content
How Can We Help?
< All Topics
Print

Community vs Future Editions or Scope

Posted
Updated
Byadmin

Purpose

CMSSPM is being built to help the broader WordPress community improve security posture without putting effective tooling out of reach for smaller businesses, consultants, nonprofits, or personal portfolio sites. The goal is to provide a genuinely useful community edition while also exploring future options that can fund ongoing maintenance, support, and development.

Where to find it

This article belongs in the Getting Started section, since it explains how the project is positioned today and what to expect from the community edition versus any future editions or support offerings. It is meant to set expectations clearly for scope, support, and sustainability.

What the community edition provides

The community edition of CMSSPM is intended to deliver practical security posture management for WordPress:

  • auditing key configuration areas,
  • highlighting misconfigurations and risks,
  • helping site owners understand where improvements can be made.

It is designed so that community users can get real value without needing a paid plan. There is no artificial “demo” limit or forced upsell in the current community edition.

At the same time, there is no dedicated funding for the community edition at this time. All work on it is done on a best-effort basis, alongside other responsibilities.

Support and expectations for community users

Because there is no current funding for the community edition:

  • Support, bug fixes, and new features are best effort only.
  • There are no guarantees of response times, issue resolution, or release cadence.
  • Communications may be delayed, and there may be periods where the project maintainer is not actively available.

The best place to reach out for questions or issues is the WordPress Support forum for the plugin. That is where users should post questions, bug reports, and feedback. The maintainer will check in there as time permits, but again, there is no guarantee of timely replies.

Community users should treat the plugin as a helpful tool, but not as a product with contracted support or uptime commitments.

Future editions and business scope

To keep CMSSPM sustainable, future editions or licensing options may be introduced for:

  • business or enterprise environments,
  • organizations that need committed response times or support,
  • larger portfolios or multi-site operations,
  • additional features that require more ongoing maintenance, infrastructure, or support.

Any such offerings would exist to:

  • help fund continued development and maintenance of the project,
  • keep the community edition viable,
  • provide stronger guarantees where organizations need them.

The intention is to keep pricing as small and practical as possible, so even business users and portfolio operators can justify it without needing a large security budget.

Notes and scope

Right now, there is one active community edition with:

  • real, functional posture management features,
  • no formal support guarantees,
  • best-effort maintenance and communication.

Future editions, support plans, or licensing options will be documented as they are introduced. Until then, users should assume:

  • the plugin is provided as-is,
  • support is best effort via the WordPress Support forum,
  • there are no formal SLAs or guarantees for response time, bug fixes, or feature delivery.
Table of Contents