behandy/blog

Risky to adopt: the package has had no release or repository activity since August 2023 and its linked repository does not match the package name. It is not deprecated or archived, and its simple dependency profile and declared license reduce some concerns, but maintenance and ownership transparency are weak.

Latest 1.1

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

Only two releases were published, both in August 2023, with no releases in the last 12 months; the package has effectively been untouched for about three years.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, reinforcing the long period without observable maintenance.

Package scaffolding

The package has no README, while the repository also has no collected README, tests, or changelog evidence; this leaves consumers with little documentation or validation context for a library.

Repo package mention

The linked repository is named fastBackEnd rather than behandy/blog, and no README package mention was collected, so the repository may not clearly back this package.

Repo popularity

The repository has zero stars and forks and only one watcher, providing no meaningful community or adoption support for the otherwise inactive project.