uiaciel/suryacms

Dependency profilecaution

There are 9 runtime dependencies, including framework, HTTP, document, image, PDF, and export libraries. This is a meaningful dependency surface for a CMS, but not unusually large enough by itself to make the release unfit.

Maintainerscaution

Only one registry account has publish access. That is a real publishing continuity concern for a user-owned project, although the same account is actively committing to the repository.

Package scaffoldingcaution

A substantial README is present, but neither the package artifact nor repository contains tests or a changelog. For a feature-rich CMS package, those missing verification and change-history resources reduce transparency.

Project backingcaution

The registry namespace and repository are owned by the same individual account, not an organization. This confirms package ownership alignment but provides no organizational maintenance redundancy.

Repo bus factorcaution

One contributor made all 8 commits in the last 3 months, giving the project a 100% top-contributor share. With user ownership rather than organization backing, this is a material continuity risk.