answear/payum-pay-u
It has a clear license, tests, regular releases, and organizational backing. Workflow references are unpinned, and the repository lacks a security policy and security scanning.
58%
Total Score
75
86
50
Health Score Breakdown
post-install-cmd and post-update-cmd scripts run during dependency installation or updates, adding operational and supply-chain exposure beyond a passive library.
The repository recorded zero commits and zero active maintainers in the last three months, which weakens evidence of ongoing maintenance after the latest release.
The repository name does not match the package and its README does not mention the package, so the link may not clearly establish package ownership.
Composer build tooling is present, but no security-scanning tools were detected, leaving an avoidable gap in maintenance hygiene.
The repository has no security policy, making vulnerability reporting and maintainer expectations less transparent.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 payum/core Version ^1.7.5 | — | — |
php-http/message Version <1.16.0 | — | — |
webmozart/assert Version ^1.11|^2.4 | — | — |
guzzlehttp/guzzle Version ^7.0 | — | — |
symfony/http-kernel Version ^7.0|^8.0 | — | — |
Weekly Downloads
Info
- Last Published
- 2 months ago
- Created
- 3 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.