zest/whoops
The MIT license, matching source repository, and lack of install scripts reduce adoption friction. Its tiny footprint may explain the absence of packaged tests and a README, while the repository does contain a README. Maintenance is the main concern, with no registry release since February 2019 and no commits in the last three months.
52%
Total Score
50
88
67
Health Score Breakdown
The latest release was published in February 2019, with no releases in the last 12 months; this is a substantial maintenance and abandonment concern.
There were no commits and no active maintainers in the last three months, indicating that ongoing maintenance capacity is currently weak.
Composer build tooling is present, but no security-scanning tooling was detected; this is a modest transparency and maintenance gap rather than a severe risk.
The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented.
The single workflow was fully analyzed with no dangerous triggers, sinks, or audit findings. Its one action reference is unpinned, which is a minor reproducibility and supply-chain hygiene gap.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Malik Umer Farooq |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 7 years ago
- Created
- 7 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.