Weave Code
Neo4J Common Laravel Package
graphaware/neo4j-common
GraphAware Neo4j Common provides shared PHP utilities for Neo4j integration, including Cypher statement and result abstractions, common interfaces, and helpers used across GraphAware’s Neo4j libraries. A lightweight foundation for building Neo4j-backed PHP applications.
Common Utility Classes for using Neo4j in PHP
Frequently asked questions about Neo4J Common
- What is graphaware/neo4j-common used for?
- It provides shared PHP utilities for Neo4j integration, including Cypher statement and result abstractions, common interfaces, and HTTP transport plumbing used across GraphAware's Neo4j libraries. It is a building block for graphaware/neo4j-php-client and the OGM, not a standalone Neo4j driver. It has no Laravel-facing surface such as a service provider, config file, or facade.
- Is graphaware/neo4j-common a Laravel package?
- No. It does not ship a Laravel service provider, configuration file, facade, or Eloquent integration. Running composer require on its own delivers no product capability. It would normally enter a Laravel application only as a transitive dependency beneath a Neo4j client.
- Does graphaware/neo4j-common support Laravel 10 or Laravel 11?
- There is no direct Laravel integration to support, so the real question is whether its PHP and Guzzle constraints are compatible with your Laravel version. Vintage libraries often pin older PHP and Guzzle majors, while Laravel 10 and 11 ship guzzlehttp/guzzle 7 on PHP 8.1 or newer. Verify the package's Composer constraints in a throwaway branch before assuming compatibility.
- Do I need to install graphaware/neo4j-common to use Neo4j with Laravel?
- No, you should not adopt it deliberately. Choose an actively maintained, Bolt-capable Neo4j client instead, and accept this package only if it arrives transitively. If it is pulled in, pin the version and run a full composer why graphaware/neo4j-common audit.
- Does graphaware/neo4j-common work with Neo4j 4.x or 5.x?
- Its abstraction layer is HTTP REST-oriented and predates Bolt, which modern Neo4j deployments expect. REST endpoints and response shapes have changed across Neo4j 3.x, 4.x, and 5.x, so an unmaintained transport layer is a likely place for silent breakage after a database upgrade. Test any transitive use against your exact Neo4j version.
- What are the licensing risks of graphaware/neo4j-common?
- GitHub reports the license as NOASSERTION, meaning it could not be automatically classified. GraphAware projects are typically permissive, but you cannot ship on an assumption. Legal review is required before making it a production dependency, including any redistribution or attribution obligations.
- Is graphaware/neo4j-common actively maintained?
- The maintenance risk is high: the project has roughly 24 stars, no dependents, no recent activity signal, and single-organization ownership. That effectively means a bus factor of one and a frozen codebase. If it breaks in your stack, your team owns the fix, so plan to vendor or fork it if you must use it.
- How should I integrate Neo4j with Laravel if not through this package?
- Define an application-owned boundary such as a GraphRepository or RelationshipQueryService interface, then implement it with a maintained Bolt-capable client. Bind that implementation in Laravel's container and mock the interface in tests. Keeping the vendor library behind this boundary preserves optionality and makes a future client swap a one-file change.
- Will graphaware/neo4j-common conflict with Laravel's Guzzle version?
- It may. Libraries of this vintage commonly pin older PHP and Guzzle majors, while Laravel 10 and 11 use Guzzle 7 on PHP 8.1 or newer. Run a Composer audit in an isolated branch to check for conflicts or a forced out-of-date install.
- What alternatives to graphaware/neo4j-common should I consider?
- Consider an actively maintained Bolt-capable client, such as the Laudis fork lineage, rather than this utility package. If the graph use case is marginal, staying on a relational store with Postgres recursive CTEs or an adjacency model may be the better migration path. The architectural decision is which Neo4j client to use, not whether to adopt neo4j-common directly.
Weaver
How can I help you explore Laravel packages today?