vldmir/laravel-iso3166

Release historydanger

Only two releases were published, both on the same day, and there have been no releases in nearly two years. This materially raises abandonment risk for a dependency.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months, consistent with the nearly two-year gap since the last push. This is the strongest maintenance concern.

Project backingcaution

The registry namespace and repository owner match, and the repository is owned by an individual. This is consistent ownership, though it provides less organizational continuity.

Repo popularitycaution

The repository has only 2 stars and no forks, indicating limited external adoption. Popularity is supporting evidence rather than a verdict, but this leaves little community signal.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a hygiene gap, not evidence that the package is unsafe.