A clear GPL-2.0 license, tests, and a readable package support adoption. The project has no security policy or scanning, which adds maintenance risk for an API integration.
42%
Total Score
50
71
83
The package has 44 releases and a historically regular median interval of about 11 days, but none in the last five years and nine months. That long release gap is strong evidence of abandonment risk.
There were zero commits and zero active maintainers in the last three months, on top of the repository's last push in 2020. This indicates no current maintenance capacity.
There are two open issues, with no new or closed issues and no pull requests in the last month. The small backlog and absent response activity reinforce the abandonment concern.
Composer is used for the build, but no security scanning tools are configured. That leaves dependency and repository-security checks less transparent.
The repository has no security policy. For an API client that handles authentication and external service communication, this is a meaningful transparency and maintenance gap.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
szeber/yapep_base Version 0.3.x-dev | — | — |
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.