geggleto/securejwt

The package includes a README, tests, and a matching repository, but no security policy or automated security scanning is reported. Its MIT declaration and lack of install scripts reduce adoption friction; avoid it for new security-sensitive JWT use.

Latest 0.0.1

Packagist

38%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

Only one release exists, published about 10 years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk for a security-focused library.

Repo commit activity

The repository has had zero commits and zero active maintainers in the last three months, consistent with the last push being about 10 years ago. The repository is not archived, but there is no observed maintenance activity.

Repo tooling

Composer build tooling is present, but no security scanning tools are reported. This is a hygiene gap for a security-sensitive package, though it does not prove the code is unsafe.

Security policy

The repository has no security policy. For a package that encrypts JWTs, this reduces transparency around vulnerability reporting and maintenance expectations.

Version stability

Version 0.0.1 is not a stable major release and has never progressed beyond the initial release. That limits maturity evidence and compounds the long maintenance gap.