loeken/cryptocompare-api-php-wrapper

Release historydanger

The latest release was about 7 years ago, with no releases in the last 12 months and only four releases overall. This is strong evidence of abandonment risk for a maintained API wrapper.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last 3 months, consistent with the repository having received no push for about 5 years. This materially increases maintenance and abandonment risk.

Maintainerscaution

Only one registry account has publish access, and the project backing signal identifies an individual owner rather than an organization. This leaves limited visible publishing capacity if that maintainer stops responding.

Repo toolingcaution

The repository uses Composer, but no security scanning tools were detected. For a small library this is a hygiene gap, though it is less serious than the lack of recent development.

Security policycaution

No security policy was found in the repository. That weakens the project's vulnerability-reporting and response transparency.