sharpapi/sharpapi-php-client

Registry deprecationdanger

Packagist marks the entire package as abandoned, making this release unsuitable for a new dependency despite having no replacement listed in the registry metadata.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers during the last 3 months, providing direct evidence that ongoing maintenance has stopped.

Release historycaution

The package has only five releases over about 2 years and 9 months, with one release in the last 12 months; the sparse cadence is consistent with its stated retirement.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools are reported. This is a transparency and maintenance gap, though it is secondary to the package's explicit abandonment.

Security policycaution

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities in a package that is no longer maintained.