smtp2go-oss/smtp2go-php
Healthy and reasonable to depend on. It has a current stable release, regular maintenance, clear licensing, tests in the repository, and organization backing; the main caveat is that all recent commits came from one contributor and the repository lacks security scanning and a security policy.
82%
Total Score
67
93
75
Health Score Breakdown
One contributor made 100% of the recent commits. Organization backing provides some ability to hand maintenance off, but no second active contributor is shown, so the project still has a meaningful concentration risk.
There were 3 commits in the last 3 months, showing recent activity, but all activity came from one maintainer. That limits evidence of broad maintenance capacity.
Composer build tooling is present, but no security scanning tools were detected. This is a transparency and maintenance-process gap, though it is not by itself evidence that the release is unsafe.
The repository has no SECURITY.md or equivalent policy, leaving vulnerability reporting and response expectations undocumented.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 guzzlehttp/guzzle Version ^7.0 | — | — |
composer/ca-bundle Version ^1.5.5 | — | — |
Weekly Downloads
Info
- Last Published
- 1 day ago
- Created
- 5 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.