yago-cms/cms

Licensedanger

No license is declared, and neither the package nor the linked repository contains a recognized license file. That leaves the legal terms for adoption unclear.

Release historydanger

The package has had 64 releases since April 2022, but none in the last 12 months and its latest release was in November 2022. This long publication gap is a material abandonment concern.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months. Combined with no releases in the last year, this indicates a substantial current-maintenance gap.

Dependency profilecaution

The release declares 11 runtime dependencies, including Laravel, GraphQL, permissions, and asset-related packages. This is a substantial integration surface but not inherently unhealthy.

Package scaffoldingcaution

The package has no README, tests, or changelog, although tests and changelogs are normally repository artifacts and their absence from a published package is expected. The missing README is still a meaningful consumer-transparency gap for a CMS package; a GitHub release exists for this version, which partly compensates for release documentation.