peyman3d/laravel-share

The README is clear, and the MIT declaration plus simple artifact make integration straightforward. The one-person project has little supporting tooling, so future compatibility and security work may be limited.

Latest 1.3.1

Packagist

40%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was published in June 2018, with no releases in the last 12 months. This long release gap is strong evidence of abandonment risk for a dependency.

Repo commit activity

There were no commits and no active maintainers in the last three months, reinforcing the long-standing maintenance gap rather than showing ongoing support.

Project backing

The repository is owned by an individual account rather than an organization, so there is no visible organizational backing to compensate for the single-maintainer structure.

Repo tooling

Composer is used for the build, which fits the package ecosystem, but no security scanning tools are present. This is a modest transparency and maintenance gap.

Security policy

The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. For a library intended for application use, that lowers transparency.