arnakoguzhan/laravel-scim-server

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months. Combined with the one-day release burst, this is meaningful evidence that current maintenance has gone quiet.

Project backingcaution

The registry namespace and repository are owned by the same individual account, so ownership is consistent, though it does not provide organizational backing.

Release historycaution

The package has 68 releases, but all 68 were published within the last 12 months on the same day, with a median interval of zero days. That burst gives limited evidence of sustained maintenance.

Repo popularitycaution

The repository has zero stars, forks, and watchers. This is weak supporting evidence, but popularity alone does not establish an adoption or maintenance problem.

Repo toolingcaution

The repository uses Composer and Make for build tasks, but no security-scanning tools are present. The missing scanning is a maintenance-hygiene gap rather than evidence that the release is unsafe.