wouterj/fred

The README, changelog, release notes, and matching license make the project relatively transparent. Its small dependency set and lack of install scripts reduce adoption friction, but ongoing maintenance evidence is weak.

Latest 0.3.0

Packagist

40%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had no release in more than 11 years, with only four releases overall and none in the last 12 months. This is strong evidence that maintenance has stopped.

Repo commit activity

There were zero commits and zero active maintainers in the last 3 months, consistent with the long release gap. The repository's last push was also more than 6 years ago.

Maintainers

Only one registry publishing maintainer is listed, and project backing identifies an individual owner rather than an organization. For a small project this is understandable, but it leaves little visible maintenance redundancy.

Repo issue activity

No issues or pull requests were opened or merged in the last month, while three issues and one pull request remain open. This adds evidence of limited ongoing attention.

Repo tooling

Composer is used as a build tool, which is appropriate for this package, but no security-scanning tool is configured. That is a modest hygiene gap rather than a standalone adoption blocker.