The package has clear licensing, tests, documentation, and no install-time scripts. Its source has seen no commits or releases for over four years, so maintenance risk is the main concern.
55%
Total Score
50
86
75
The package has 22 releases and historically released about every 28 days, but its latest release was over four years ago and there were no releases in the last 12 months. This materially raises abandonment risk.
The repository recorded no commits and no active maintainers in the last three months, consistent with the extended release gap. The repository is not archived, but there is no recent activity showing ongoing maintenance.
The repository uses Composer build tooling, but no security scanning tools were detected. That leaves dependency and source checks less evident than in a project with automated scanning.
No security policy was found in the repository. This is a transparency and response-process gap, though it is less severe than the absence of recent maintenance.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
everest/http Version ^2.0 | — | — |
everest/container Version ^2.0 | — | — |
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 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.