lyhiving/ragflow-laravel

Usable with caveats: the repository is active-looking, tested, licensed, and correctly linked to the package, but release and commit activity stopped about 15 months ago. The pre-1.0 version and missing security policy add maintenance risk.

Latest v0.6

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

There were no commits and no active maintainers in the last three months, following a last push about 15 months ago. This is the strongest evidence that maintenance may have stalled.

Project backing

The registry namespace and repository owner match, and the project is owned by an individual rather than an organization. That is consistent ownership evidence, but it provides limited redundancy if the maintainer becomes unavailable.

Release history

The package has five releases, but its latest release was about 15 months ago and it has had no releases in the last 12 months. This makes ongoing maintenance uncertain despite the earlier release history.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a hygiene gap, while the build tooling and repository tests provide some compensating transparency.

Security policy

The repository has no security policy. This reduces transparency for reporting and handling vulnerabilities, although it is a process gap rather than evidence that the package is unsafe.