whoops/phalcon
The small, focused package is easy to inspect, with an MIT declaration, a matching repository, and only one runtime dependency. Treat it as legacy code and avoid relying on it for a newly adopted integration unless you can maintain the adapter yourself.
38%
Total Score
50
100
70
50
Health Score Breakdown
The package has only two releases, both from 2015, with no release in nearly 11 years. That strongly raises abandonment risk despite the stable v2.0.0 version.
The repository has had zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating no observed ongoing maintenance.
There are no open issues or pull requests and no recent activity. While this can be normal for a tiny adapter, alongside the stale releases it provides no evidence of active support.
The repository is not archived, which avoids a stronger abandonment signal, but its last push was in January 2016 and still reflects very old source activity.
The repository has no security policy. This is a transparency gap, though the package is small and the absence is less significant than its prolonged maintenance inactivity.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Tim Robertson |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 filp/whoops Version @dev | — | — |
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.