davidkiarie/next-layer-jwt-package
The MIT license and stable versioning make its legal and release shape clear. A tiny README, no security policy, and no security scanning leave little guidance or oversight.
38%
Total Score
0
69
75
Health Score Breakdown
The package has had no release in roughly four years, despite seven releases clustered within hours in February 2022. This strongly indicates abandonment risk.
The repository has recorded zero commits and zero active maintainers in the last three months, with its last push in February 2022. This confirms that maintenance is not merely slow but inactive.
The artifact includes a README, but it is only 76 characters and provides little integration guidance. The absence of tests and a changelog is normal for a published artifact and is not penalized.
The linked repository name does not match the package name and its README does not mention the package, so the source may not clearly belong to this release.
Composer is used for builds, but no security-scanning tooling is present. For an authentication package, that is a meaningful oversight gap.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 david-macharia |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 4 years ago
- Created
- 4 years ago
Are You Affected?
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.