Laravel Azampay
62%
Total Score
75
100
83
75
The package is 327 days old but has only one release, with no demonstrated release cadence beyond the initial publication. That leaves long-term maintenance and compatibility uncertain.
The repository recorded zero commits and zero active maintainers during the last three months. For a payments integration, this lack of recent development is a meaningful maintenance concern.
The repository has zero stars, forks, and watchers, providing no community adoption signal. Popularity is only supporting evidence, but its absence adds uncertainty for a young package.
Composer is used as the build tool, but no security-scanning tools are configured. The missing scanning is a hygiene gap, though it is not by itself evidence that the package is unsafe.
The repository has no security policy. This reduces transparency about how vulnerabilities should be reported, especially for a package handling payment integrations.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.5 | — | — |
illuminate/contracts Version ^12.0 | — | — |
spatie/laravel-package-tools Version ^1.16 | — | — |
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.