vinelab/neo4jphp

Release historydanger

This is the only release, published in October 2014, with no releases in the last 12 months. That long gap strongly indicates abandonment despite the package remaining undeclared as deprecated.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history and providing no evidence of current maintenance.

Maintainerscaution

Only one registry account has publish access. The organization-backed repository provides some context, but the observed release and commit inactivity leaves a thin maintenance base.

Repo toolingcaution

Composer and Phing provide build tooling, but no security-scanning tools are configured. The build setup is a modest positive, while the missing scanning reduces maintenance assurance.

Security policycaution

The repository has no security policy. This is a transparency and response-process gap, especially for a client handling database connections, though it is secondary to the prolonged inactivity.