levidurfee/resend

The tiny three-file repository has no security policy, offering little transparency for a package consumers may integrate. MIT licensing and no install-time scripts reduce adoption risk, but an active fork is safer.

Latest v0.1.0

Packagist

38%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

This is the only release, published about two years and seven months ago, with no releases in the last 12 months. That leaves little evidence of ongoing maintenance.

Repo commit activity

There were no commits or active maintainers in the last three months, consistent with the long gap since the last push and raising abandonment risk.

Package file tree

The artifact and repository each contain only three files, including a single source file and composer.json. This is a very small project footprint and provides limited evidence of maturity.

Project backing

The package and repository are owned by the same individual account, so ownership is consistent, but there is no organizational backing shown to offset the single-person maintenance risk.

Repo popularity

The repository has zero stars and forks and only one watcher. Popularity is not decisive, but this provides no supporting evidence of community use or review.