pyro/custom-install

Release historydanger

The package has only two releases, both published in March 2020, and none in the last 12 months. This long period without releases is strong evidence of abandonment risk.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months. Combined with the old last release, this indicates no current maintenance capacity.

Project backingcaution

The repository owner is an organization, which provides some project backing context, but the observed release and commit inactivity shows that backing has not translated into current maintenance.

Repo popularitycaution

The repository has zero stars and forks and only one watcher. Popularity is not decisive, but these figures provide little supporting evidence of adoption or community oversight.

Repo toolingcaution

The repository uses Composer, which fits the package ecosystem, but it has no security scanning tools. This is a modest transparency and maintenance-hygiene gap.