Bizimhesap B2b Entegrasyonu.
58%
Total Score
caution
No releases in over two years and no commits in the last three months make maintenance the main concern.
The repository is owned by the same individual account as the registry namespace. This provides consistent ownership context, but it does not provide organizational backing or redundancy.
The package has 13 releases since April 2021, but none in the last 12 months and its latest release was in June 2024. This is a meaningful maintenance concern for a package integrating an external business API.
There were zero commits and zero active maintainers in the last three months. Together with no releases in the last year, this indicates currently inactive maintenance.
Composer is used for builds, but no security-scanning tool was detected. The missing scanner is a hygiene gap, not evidence that the package is unsafe by itself.
The linked repository is not archived, although its last push was in June 2024. The active repository status is reassuring, while the old push date is consistent with the maintenance concern from release and commit history.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version * | — | — |
illuminate/support Version * | — | — |
giggsey/libphonenumber-for-php Version ^8.12 | — | — |
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.