nexmo/client
Security coverage is thin, with no repository security policy or scanning tools. Licensing, release notes, organization backing, and a non-archived repository provide useful transparency.
58%
Total Score
75
86
50
Health Score Breakdown
The package has six releases but none in nearly six years, with zero releases in the last 12 months. This is a meaningful maintenance concern despite its earlier release history.
The repository had zero commits and zero active maintainers in the last three months. That supports the concern that current maintenance may be limited.
Composer build tooling is present, but no security-scanning tools were detected. The project has basic build support but limited visible security automation.
The linked repository has no security policy. This weakens vulnerability-reporting transparency, though it is a hygiene gap rather than evidence that the package is unsafe.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Tim Lytle |
| Michael Heap |
| Lorna Mitchell |
| Chris Tankersley |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 guzzlehttp/guzzle Version ^7.0 | — | — |
nexmo/client-core Version ^2.0 | — | — |
Weekly Downloads
Info
- Last Published
- 6 years ago
- Created
- 7 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.