sjs/neos-mcp-feature-set-test

Release historycaution

The package is 100 days old with only one release, so there is not yet enough release history to demonstrate sustained maintenance. Its recent creation partly explains the limited record.

Repo commit activitycaution

There were no commits or active maintainers in the three months covered, beyond the initial repository push. For a package only 100 days old this is not proof of abandonment, but it leaves ongoing maintenance unproven.

Repo package mentioncaution

The repository name does not match the package name and its README does not mention the package, so the link may not clearly establish that the repository belongs to this release.

Repo toolingcaution

Composer is used as the build tool, which fits the package ecosystem, but no security scanning tooling was detected. The missing scanning is a modest transparency and maintenance concern rather than a severe risk.

Security policycaution

The repository has no security policy. For a small testing feature set this is a limited process gap, but it reduces clarity about vulnerability reporting and maintenance response.