trippo/laravel-openstack

Release historydanger

The latest release was published more than five years ago, with no releases in the last 12 months. The 12-release history shows an earlier burst of activity but does not compensate for the prolonged release gap.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers over the last three months, consistent with the package's multi-year release inactivity and indicating weak ongoing maintenance.

Repo issue activitycaution

There were no new or merged pull requests and no issue activity in the last month. This is supporting evidence of inactivity, although the null open-issues count limits what can be concluded about unresolved work.

Repo popularitycaution

The repository has zero stars and one fork, offering little evidence of a broad user or contributor base. Popularity is supporting evidence rather than a verdict, so this reinforces the maintenance concern without determining it alone.

Repo toolingcaution

Composer is present as the build tool, but no security scanning tools were detected. The missing scanning is a modest hygiene gap, while the package's small five-file tree limits the significance of that omission.