breadlesscode/neos-simple-editor-extend

Maintainerscaution

Only one registry account has publish access. Because the repository is owned by a user rather than an organization, this represents a genuinely thin publishing base and increases continuity risk.

Project backingcaution

The registry namespace and repository owner both identify breadlesscode, and the repository is user-owned. The matching ownership provides some continuity evidence, but there is no organization backing to offset the single-maintainer risk.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers in the last three months. Although a release and push occurred recently, the absent sustained activity is a meaningful maintenance concern.

Repo issue activitycaution

There are two open issues and three open pull requests, but none were opened or closed in the last month. This suggests limited current responsiveness.

Repo toolingcaution

Composer is used for builds, but no security scanning tools are configured. The missing scanning is a transparency and maintenance gap, though it is not severe enough alone to make the package unfit.