solve/project
The MIT license, matching repository, and small dependency set support straightforward adoption. Install-time scripts and the lack of security tooling add maintenance overhead, while organization backing does not offset the stale project.
34%
Total Score
50
63
50
Health Score Breakdown
The latest release was on November 24, 2014, and there have been no releases in roughly 11 years 10 months. This strongly indicates abandonment risk despite 12 historical releases.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long-stale release history. No newer maintenance activity is visible to compensate for that gap.
The package runs both post-install and post-update scripts, increasing installation complexity and maintenance surface. The signal does not show those scripts are unsafe, so this is a maintenance caution rather than a severe risk.
Composer build tooling is present, but no security scanning tools are reported. That is a modest transparency and maintenance gap, especially alongside the absence of recent activity.
The linked repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This matters more for a package with no recent maintenance activity.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Alexandr Viniychuk |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 solve/solve Version * | — | — |
Weekly Downloads
Info
- Last Published
- 11 years ago
- Created
- 11 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.