raymondthedev/linkedin-api-php-client

Release historydanger

The latest release was published about five years ago, with no releases in the last 12 months. Fourteen total releases show some historical work, but the prolonged gap materially raises abandonment risk.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release hiatus and leaving current maintenance capacity unproven.

Repo popularitycaution

The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but these values provide no community signal to compensate for the lack of recent maintenance.

Security policycaution

No security policy is present, so vulnerability reporting expectations are unclear. This is a transparency and response-process gap, though it is less severe than the maintenance inactivity.

Workflow auditcaution

No GitHub Actions workflows were present, so there were no workflow hazards to flag. This also provides no evidence of active automated maintenance or release controls.