hubertprein/craft-jwtmanager
Risky to adopt for a new project: the package has had no release or commit activity for over seven years. It remains licensed, documented, and not deprecated or archived, but its inactivity and lack of security and testing practices create substantial maintenance risk.
42%
Total Score
0
75
75
Health Score Breakdown
The latest release was published over seven years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk for a package handling authentication tokens.
The repository recorded no commits and had no active maintainers in the last three months, reinforcing that maintenance has effectively stopped.
The repository uses Composer but has no security scanning tools. For authentication-related code, the absence of automated security checks is a meaningful hygiene gap.
The repository is not archived, which is a positive sign, but its last push was over seven years ago and does not offset the observed inactivity.
No security policy was found for a package that manages JWT login and refresh tokens. This reduces transparency and makes vulnerability reporting less clear.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 craftcms/cms Version ^3.0.0-beta.20 | — | — |
firebase/php-jwt Version ^4.0.0 | — | — |
mobiledetect/mobiledetectlib Version ^2.8 | — | — |
Weekly Downloads
Info
- Last Published
- 7 years ago
- Created
- 8 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.