ericychu/forsun-laravel

The small user base and absent security tooling add little reassurance. A license, working README, matching repository, and no install scripts reduce adoption friction, but pinning this old release leaves significant maintenance risk.

Latest v1.0.6

Packagist

40%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had no release in nearly eight years: its latest release was published in October 2018, with zero releases in the last 12 months. This is strong evidence of abandonment risk.

Repo commit activity

There were zero commits and zero active maintainers in the last three months, following an already long period without releases. This indicates that fixes and compatibility updates are unlikely.

Project backing

The repository is owned by an individual rather than an organization, so the single registry maintainer is not backed by an organizational project structure. This provides limited continuity assurance.

Repo popularity

The repository has zero stars and forks and only one watcher, offering little evidence of a broad user or contributor community. Popularity is supporting evidence, but this reinforces the maintenance concerns.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. The absence of scanning is a hygiene gap, especially alongside the lack of recent maintenance.