froccsos/billingo-api-connector
The package has a clear README, an MIT license, and no install-time scripts. Its single-user ownership and missing security policy provide little evidence of ongoing oversight, while the small dependency set limits complexity.
44%
Total Score
25
100
81
75
Health Score Breakdown
The latest release was nearly six years ago, with no releases in the last 12 months. This is strong evidence that maintenance has stopped, despite a reasonable historical release cadence.
The repository recorded zero commits and zero active maintainers in the last three months, corroborating the long release gap and increasing abandonment risk.
Only one registry maintainer is listed, leaving a thin publishing base. This is more concerning alongside the absence of recent repository activity, though it does not by itself prove the project is unmaintained.
Composer build tooling is present, but no security scanning tools were detected. That weakens ongoing assurance for a package handling API authentication and requests.
The repository has no security policy, reducing transparency for reporting vulnerabilities in an API connector. This is a hygiene and oversight gap, not evidence of malicious behavior.
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 || ^5 | — | — |
guzzlehttp/guzzle Version ^6 || ^7 | — | — |
symfony/options-resolver Version ^5 | — | — |
Weekly Downloads
Info
- Last Published
- 5 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.