horde/jwt

Clear documentation, tests, and release notes make integration straightforward. The short history, one-contributor recent activity, and absent security controls leave meaningful maturity and maintenance uncertainty.

Latest v1.0.0

Packagist

70%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package is only 154 days old with two releases and a median interval of about 58 days, so its long-term maintenance pattern is not yet established.

Repo bus factor

All recent commits came from one contributor, creating concentration risk; organization ownership provides some handoff capacity but no second active contributor is shown.

Repo commit activity

Only one commit was recorded in the last three months from one active maintainer, which is thin evidence of ongoing development for a package this new.

Repo tooling

Composer build tooling is present, but no security-scanning tool was detected, leaving a security-process gap for a library that handles JWT signing and verification.

Security policy

The repository has no security policy, reducing transparency about how vulnerabilities should be reported and handled.