sgpatil/orientdb

The package is clearly documented, licensed, and includes tests, but maintenance appears to have stopped long ago. Its very small release history and absent security policy leave substantial adoption risk for a Laravel database integration.

Latest v0.0.2

Packagist

32%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only 2 releases, with no releases in the last 12 months, and its latest release was about 11 years ago. This is strong evidence of abandonment risk for a framework integration.

Repository archived

The repository is not marked archived, which avoids the strongest abandonment signal, but it was last pushed about 10 years ago. The lack of recent repository activity still materially lowers confidence in ongoing maintenance.

Project backing

The registry namespace and repository are owned by the same individual account. This is consistent ownership evidence, but it does not provide organizational backing or compensate for the long maintenance gap.

Repo issue activity

There has been no issue or pull-request activity in the last month, with one issue still open. This provides no evidence of active support and is consistent with the long inactivity shown elsewhere.

Repo popularity

The repository has 11 stars and 3 forks, providing limited supporting adoption evidence. Popularity is too small to offset the prolonged inactivity.