poyrazenes/administrative-company-operations

Release historydanger

The latest release was published nearly 3 years ago, with no releases in the last 12 months. This is substantial evidence of stalled maintenance for a production dependency.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last 3 months. Combined with the stale release history, this materially raises abandonment risk.

Maintainerscaution

Registry publishing access is held by one individual. That is a limited operational base and increases continuity risk, with no organization backing shown by the provided project context.

Repo popularitycaution

The repository has zero stars and forks and only one watcher. Popularity is not decisive, but this offers little supporting evidence of community review or shared maintenance.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools are configured. This is a modest transparency and maintenance gap for a package with application-facing Laravel code.