nuclearcms/nuclear.cli

Release historydanger

Only one release exists, published in June 2016, with no releases in the last 12 months. This is strong evidence that the package is abandoned rather than actively maintained.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months. Combined with the old last push, this indicates severe maintenance inactivity.

Repo popularitycaution

The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but these counts provide no community signal to offset the maintenance concerns.

Repo toolingcaution

Composer is used for builds, which fits the ecosystem, but no security scanning tools are present. The missing scanning is a modest transparency and hygiene concern for a dependency.

Repository archivedcaution

The repository is not archived, which is a modest positive, but its last push was in June 2016 and does not offset the broader inactivity evidence.