flow/email-checker

The repository has no security policy or scanning, and its tiny footprint offers little evidence of ongoing support. MIT licensing, a README, and no install scripts reduce adoption friction.

Latest 0.3.0

Packagist

31%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was in November 2013, with no releases in the last 12 months and no meaningful recent release activity. This is strong evidence of abandonment for a library dependency.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, while its last push was in April 2014. The long inactivity materially raises maintenance risk.

Repo package mention

The linked repository name does not match the package name and its README does not mention the package, so ownership of the published package is not clearly demonstrated. This is a transparency concern despite the repository being linked.

Repo popularity

The repository has only 2 stars and no forks, providing little supporting evidence of broad review or community involvement. Popularity is not required, but this does not offset the inactivity.

Security policy

The repository has no security policy and no documented process for reporting vulnerabilities. For a package that connects to mail servers, this weakens transparency and support expectations.