jiny/auth-api

It has a clear MIT license, a matching organization-backed repository, and no install-time scripts. The small release history and no commits in the last three months leave maintenance uncertain, while the missing security policy is a modest transparency gap.

Latest 0.2

Packagist

54%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

Only two releases appeared, both around February 2025, with no releases in the last 12 months despite the package being about 589 days old. This is meaningful evidence of limited ongoing maintenance.

Repo commit activity

There were no commits and no active maintainers in the last three months. Combined with the old release history, this raises a real risk that maintenance has stalled.

Repo tooling

Composer is used for the build, but no security-scanning tooling is present. This is a modest hygiene gap, not evidence that the package is unsafe or abandoned.

Security policy

The repository has no security policy, which reduces transparency about vulnerability reporting and response. The small package scope limits the severity of this gap.

Version stability

Version 0.2 is not a stable major release, so the public API may still change. The package is not marked prerelease, which partially offsets the concern but does not establish maturity.