fruitware/robokassa-bundle
Its MIT license and organization-owned repository provide useful context. The small project has no security policy, and its repository does not clearly identify the package.
39%
Total Score
50
72
75
Health Score Breakdown
Only two releases appeared, both in October 2017, with no release in nearly nine years. That strongly raises abandonment risk despite the stable 1.0.1 version.
The repository recorded zero commits and zero active maintainers in the last three months. Combined with the old release history, this is strong evidence of inactive maintenance.
The repository name does not match the package name and its README does not mention the package. That creates uncertainty about whether the repository is the package's authoritative home.
The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but the absence of any visible community adoption adds to the uncertainty around this old package.
Composer is used for the build, but no security scanning tools were detected. That is a modest transparency and maintenance gap for a payment-related bundle.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Coroliov Oleg |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 guzzlehttp/guzzle Version ~6.0 | — | — |
jms/payment-core-bundle Version ~1.0 | — | — |
symfony/framework-bundle Version >=2.1,<3.0 | — | — |
Weekly Downloads
Info
- Last Published
- 8 years ago
- Created
- 8 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.