adrianmtanase/laravel-vector-store

Project backingcaution

The package and repository are owned by the same individual account, so the single registry maintainer reflects the project's actual ownership rather than an organization-backed release process.

Release historycaution

The latest release was over two years ago, with no releases in the last 12 months. Its earlier eight-release history shows initial activity but does not offset the prolonged gap.

Repo commit activitycaution

There were no commits and no active maintainers in the last three months, consistent with a project that has been inactive for over two years.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tool was detected. That is a modest transparency and maintenance gap, not evidence that the package is unsafe.

Security policycaution

The repository has no security policy, leaving vulnerability-reporting expectations undocumented. This matters more for a package handling external vector-database integrations, though it is not severe alone.