voov/billingo-api-connector
The package has a clear README, MIT licensing, and a small, coherent dependency set. Its repository is not archived, but it lacks tests and security scanning to support ongoing maintenance.
43%
Total Score
25
75
50
Health Score Breakdown
The latest release was nearly 7 years ago, with no releases in the last 12 months. That long gap is strong evidence of abandonment risk for an API connector.
The repository recorded no commits and no active maintainers in the last 3 months, consistent with the release history showing several years without a new version.
There were 22 open issues and 3 open pull requests, but no new or closed issues or merged pull requests in the last month, suggesting unresolved maintenance demand.
Composer build tooling is present, but no security scanning tools were detected. The absence of scanning is a maintenance and transparency gap for a package handling API authentication.
The repository has no security policy, leaving users without a documented process for reporting or handling vulnerabilities. This compounds the concern created by the lack of recent maintenance.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Daniel Fekete |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 firebase/php-jwt Version ^3.0 | — | — |
guzzlehttp/guzzle Version ^6.0 | — | — |
symfony/options-resolver Version 4.* | — | — |
Weekly Downloads
Info
- Last Published
- 7 years ago
- Created
- 10 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.