matt-bartlett/php-spotify-api

Release historydanger

Only three releases were published, all early in the package's life, with no release in the last 12 months and the latest release dating to March 2020. This is strong evidence of prolonged inactivity.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months, consistent with a project that has been dormant for years. This materially raises abandonment risk.

Maintainerscaution

Only one registry account has publish access. The matching personal repository makes this understandable, but it also indicates limited publishing redundancy.

Project backingcaution

The registry namespace and repository are owned by the same individual account, so the package's ownership is internally consistent. There is no organizational backing shown to offset the single-person maintenance risk.

Repo toolingcaution

The repository uses Composer, but no security scanning tools were detected. The missing scanning is a hygiene weakness, not evidence that the package is unsafe or unmaintained by itself.