chargily/chargily-pro
The MIT license, tests, release notes, and organization-backed repository improve transparency. The zero recent commits and repository naming mismatch leave maintenance and package ownership less certain.
58%
Total Score
75
100
88
75
Health Score Breakdown
The repository recorded zero commits and zero active maintainers in the last three months. The same-day push and release history provide some counterevidence, but recent development capacity remains uncertain.
The repository name does not match the package name and its README does not mention the package, so the package-to-source relationship is not clearly established.
Composer build tooling is present, but no security scanning tools were detected. This is a modest hygiene gap rather than evidence of unsafe behavior.
The repository has no security policy, leaving reporting and response expectations undocumented for a library that handles API credentials and payment-related integrations.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 ChargilyDev |
| Mohammed Boubazine |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 nesbot/carbon Version ^3.11 | — | — |
guzzlehttp/guzzle Version ^7.10 | — | — |
symfony/validator Version ^8.0 | — | — |
illuminate/support Version ^12.41 | — | — |
Weekly Downloads
Info
- Last Published
- 7 days ago
- Created
- 8 months 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.