webservco/controller
Its MIT licensing and matching repository make ownership and reuse clear. The organization-backed project is not archived, but it has no releases in about 19 months and no commits in the last 3 months. The single registry maintainer and absent security tooling add modest caution.
61%
Total Score
67
88
83
Health Score Breakdown
Only one account has registry publishing access, which is a modest resilience concern. The repository is organization-owned, so this is less concerning than a lone individual-owned project.
The package has had no release in about 19 months, despite 26 releases since July 2023. This is a meaningful maintenance concern for a library dependency.
There were no commits and no active maintainers in the last 3 months. Combined with the long release gap, this points to paused maintenance.
Composer build tooling is present, but no security scanning tools were detected. This is a hygiene gap, not evidence that the package is unsafe.
The repository has no security policy. For a library, this reduces transparency around vulnerability reporting but does not by itself indicate abandonment.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Radu Maier |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 webservco/view Version ^1 | — | — |
webservco/route Version ^1 | — | — |
webservco/reflection Version ^1 | — | — |
psr/http-server-handler Version ^1 | — | — |
webservco/dependency-container Version ^1 | — | — |
Weekly Downloads
Info
- Last Published
- 1 year ago
- Created
- 3 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.