sjs/neos-mcp-oauth

Project backingcaution

The repository is owned by an individual account rather than an organization, so there is no provided evidence of organizational maintenance capacity. The package namespace and repository owner are consistent enough to avoid treating this as a mismatch.

Release historycaution

This package has only one release, published 98 days ago, so there is not enough release history to establish mature maintenance. No other provided signal demonstrates an established release process.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers in the last three months. For an authentication package, that absence of observed maintenance is a meaningful concern even though the project is still relatively new.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tooling was detected. That weakens the project's transparency and routine security hygiene for an OAuth component.

Security policycaution

No repository security policy was found. For a package handling OAuth authorization and tokens, this is a genuine disclosure and maintenance-process gap.