try make a composer package
40%
Total Score
25
63
50
The package has had only two releases, with the latest published in October 2018 and none in the last 12 months. This long period without releases is strong evidence of abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history showing no activity since October 2018.
Only one registry account has publish access, and the repository is owned by an individual rather than an organization. This leaves a thin apparent publishing base, although access records do not prove who actively maintains the project.
Composer build tooling is present, but no security-scanning tools are configured. The missing scanning is a hygiene gap rather than evidence that the package is unsafe.
The repository has no security policy, reducing transparency for a package that handles SMTP validation and connections. This is a secondary concern beside the much stronger maintenance gap.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.