Package Health/amirjavadikia/authentication

amirjavadikia/authentication

The MIT license and absence of install-time scripts reduce adoption risk. The small repository, missing README, absent tests, and lack of a security policy provide little evidence of engineering discipline or ongoing support.

Latest 0.1.0

Packagist

40%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

This package has only one release, published about five years ago, with no releases in the last 12 months. That is strong evidence of abandonment risk despite the repository not being archived.

Maintainers

A single registry maintainer is consistent with this being a user-owned project, but it leaves little visible publishing capacity if that maintainer becomes inactive.

Package scaffolding

The artifact has no README, tests, or changelog, while the repository also reports no tests or changelog. Missing tests and project documentation reduce transparency for a library consumers must integrate, although compiled-artifact packaging can make some omissions normal.

Repo popularity

The repository has zero stars and forks and only one watcher. Popularity is not required for health, but these figures provide no supporting evidence of adoption or community oversight.

Repo tooling

Composer is used for the build, which is appropriate, but no security-scanning tooling is reported. This is a modest transparency and maintenance gap rather than evidence of a direct defect.