jepi/exception
The package is small, clearly licensed, and has no install-time scripts or workflow findings. Its minimal project backing and absent security policy leave little evidence of ongoing care or support.
15%
Total Score
25
57
83
Health Score Breakdown
Packagist marks the entire package as abandoned, with no replacement named. This is a severe adoption risk because the registry explicitly signals that the package should no longer be depended on.
There has been only one release, published over 10 years ago, with no releases in the last 12 months. This provides strong evidence of abandonment rather than an actively maintained stable package.
The repository recorded zero commits and zero active maintainers in the last 3 months. Combined with the old release history, this indicates no current maintenance capacity.
Only one registry maintainer is listed, and the repository is user-owned rather than organization-backed. This leaves a thin apparent support base, especially alongside the absence of recent activity.
The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these values provide no meaningful community support signal.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Jepi Humet |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 jepi/io Version * | — | — |
Weekly Downloads
Info
- Last Published
- 10 years ago
- Created
- 10 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.