jmf/spam-evaluation-client
The project has one registry maintainer, no security policy, and no security-scanning tools, leaving limited resilience and transparency. Its license, repository linkage, tests, stable versioning, and non-deprecated status are solid.
62%
Total Score
50
88
50
Health Score Breakdown
One registry maintainer is responsible for publishing the package. Because the repository is owned by an individual rather than an organization, this leaves a thin publishing base.
Only two releases have been published over about 870 days, with one release in the last 12 months and a median interval of about 631 days; this indicates a slow maintenance cadence.
The repository recorded zero commits and zero active maintainers in the last three months, which is a concrete sign of limited recent maintenance.
Composer build tooling is present, but no security-scanning tools were detected. This is a modest transparency and maintenance gap rather than a severe risk on its own.
The repository has no security policy, so users have no documented channel or process for reporting vulnerabilities.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Jean-Michel Feurprier |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 webmozart/assert Version ^1.0|^2.0 | — | — |
jmf/spam-evaluation-shared Version ^2.0 | — | — |
symfony/http-client-contracts Version ^3.0 | — | — |
Weekly Downloads
Info
- Last Published
- 8 months 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.