vaened/laravel-structer

Release historydanger

The package has had no release in over two years and none in the last 12 months, despite seven releases shortly after launch. This is strong evidence of abandonment risk.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months, consistent with the long release gap. This materially increases the risk that compatibility issues will remain unresolved.

Project backingcaution

The package and repository are owned by the same individual account, which supports identity matching but does not provide organizational backing or additional maintenance capacity.

Repo popularitycaution

The repository has zero stars and forks and only one watcher. Popularity is not required for health, but these counters provide no supporting evidence of broad community adoption.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. This is a modest repository hygiene gap rather than a standalone dependency risk.