chris911/slim-api-auth

Release historydanger

The package has had no release in over 12 years, with all four releases clustered on one day in March 2014. That is strong evidence of abandonment for a library dependency.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, while its last push was in March 2014. This confirms the long release gap is not just a registry artifact.

Repo issue activitycaution

There has been no issue or pull-request activity in the last month and no open work. Although a quiet issue tracker can be benign, here it reinforces the absence of ongoing maintenance.

Repo package mentioncaution

The repository name matches the package, reducing the risk of an unrelated source repository, but the README does not mention the package name. This mismatch creates a minor provenance concern.

Repo toolingcaution

Composer is used for the build, which is appropriate for this Packagist package, but no security scanning tool is present. That is a modest supply-chain hygiene gap rather than evidence of abandonment by itself.