firehed/jwt
The package has a clear MIT license, a useful README, repository tests, and release notes for this version. Its small project footprint and limited security tooling leave less evidence of ongoing oversight.
68%
Total Score
33
100
89
75
Health Score Breakdown
There were zero commits and zero active maintainers in the last three months. Combined with the roughly two-year release gap, this is the strongest maintenance concern.
The repository is owned by an individual user rather than an organization, so the single registry maintainer represents a genuinely narrow visible ownership base.
The package has existed since April 2015 with 10 releases, but it has had no release in about two years and no releases in the last 12 months. That weakens evidence of current maintenance without showing abandonment by itself.
The repository has four open issues and one open pull request, but none were opened or closed in the last month. That suggests limited current responsiveness.
Composer build tooling is present, but no security-scanning tool was detected. This is a modest transparency and oversight gap rather than evidence that the package is unsafe.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Eric Stern |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 firehed/security Version ^1.0 | — | — |
Weekly Downloads
Info
- Last Published
- 2 years ago
- Created
- 11 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.