the-orville/exceptions
The small dependency surface and stable 1.0.0 release keep integration simple. Repository tests and release notes add transparency, but the long single-release history and absent recent commits limit confidence in ongoing maintenance.
62%
Total Score
50
63
50
Health Score Breakdown
The package runs post-install and post-update Composer scripts. Install-time execution adds dependency and reproducibility concerns, although no evidence here shows that the scripts are unsafe.
This is the only release, published 1014 days ago, with no releases in the last 12 months. That leaves little evidence of sustained registry maintenance despite the repository showing some recent activity.
The repository recorded zero commits and zero active maintainers in the last three months. Recent pull-request activity partly offsets this, but it does not demonstrate sustained implementation work.
The repository name does not match the package name and its README does not mention the package. This may reflect a subpackage or monorepo, but the linkage is not clearly demonstrated by the collected evidence.
The project uses Composer and Make, but no security-scanning tooling is reported. This is a modest transparency gap rather than evidence that the package is unsafe.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Cees-Jan Kiewiet |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 2 years ago
- Created
- 2 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.