nuclearcms/nuclear.vendor

Release historydanger

This is the only release, published nearly 10 years ago, with no releases in the past 12 months. That strongly indicates the package is no longer actively maintained.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the past three months, consistent with the long release gap and increasing abandonment risk.

Package file treecaution

The published artifact contains only three files—composer.json, LICENSE, and .gitignore—while the linked repository contains the source tree. This makes the release difficult to inspect and understand from the package alone.

Package scaffoldingcaution

The artifact has no README or tests, while the repository has a changelog and uses GitHub releases. The missing consumer documentation and tests reduce transparency, despite the repository changelog.

Repo popularitycaution

The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but this provides no additional sign of adoption or community support.