A single registry maintainer, no security scanning, and almost no repository adoption leave limited evidence of ongoing support. The MIT license, clear README, matching repository, and no install scripts reduce adoption friction.
43%
Total Score
33
100
72
75
The latest release was in January 2019, with zero releases in the last 12 months despite a package age of nearly 10 years. This is strong evidence of abandonment risk for a payment integration.
There were no commits and no active maintainers in the last three months, consistent with repository activity having stopped years ago.
Only one account has registry publish access, leaving little visible publishing redundancy. This is more concerning because the project is user-owned rather than organization-backed.
The registry namespace and repository owner match, but the owner is an individual account rather than an organization, providing limited visible backing for long-term maintenance.
The repository reports zero stars, forks, and watchers, offering no meaningful community-adoption evidence. Popularity is supporting evidence rather than a verdict, so this is a secondary concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ~5.0 | — | — |
illuminate/contracts Version ~5.0 | — | — |
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.