openfed/openfed-project
Regular releases and organization backing support continued maintenance, while the package is clearly documented and has no install-time scripts. Resolve the conflicting license information and note that repository activity has been absent for the last three months.
67%
Total Score
75
100
88
83
Health Score Breakdown
The manifest declares GPL-2.0-or-later, but the artifact and repository license file are detected as BSD-3-Clause. A license file exists, so this is a concrete consistency concern rather than an absence of licensing.
The repository recorded no commits and no active maintainers in the last three months. The recent release history partly offsets this, but the lack of current source activity remains a maintenance caution.
Composer is used as the build tool, but no security scanning tools are reported. The missing scanning is a modest hygiene gap rather than a direct dependency-health failure.
The linked repository has no security policy. That weakens vulnerability-reporting transparency, although it does not by itself show abandonment.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Blue4You |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 composer/installers Version ^2.3 | — | — |
wikimedia/composer-merge-plugin Version ^2.1 | — | — |
oomphinc/composer-installers-extender Version ^2.0 | — | — |
Weekly Downloads
Info
- Last Published
- 7 months ago
- Created
- 4 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.