nuclearcms/nuclear.core

Release historydanger

There has been only one release, published over 10 years ago, with none in the last 12 months. That strongly indicates the package is no longer maintained.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the decade-long release gap and indicating no current maintenance capacity.

Package file treecaution

The published artifact contains only LICENSE and composer.json, while the linked repository contains the actual source tree. This unusually sparse artifact raises concern about whether the release is complete for consumers.

Package scaffoldingcaution

The published package has no README, tests, or changelog; the repository also has no tests or changelog. The GitHub release support is a small positive, but it does not compensate for the lack of consumer guidance and validation.

Repo issue activitycaution

There has been no issue or pull request activity in the last month. Combined with the absence of recent commits, this provides no sign of active project support.