The package is small, clearly identified, licensed, and has no install-time scripts. It lacks a security policy, while repository activity has effectively stopped since the initial release, making future fixes uncertain.
52%
Total Score
50
100
88
75
The repository is owned by an individual account rather than an organization, so there is no visible organizational backing to offset the thin maintenance evidence.
This is the package's only release, published about 19 months ago, with no releases in the last 12 months. That limits evidence of ongoing maintenance, although the package is not deprecated.
The repository recorded zero commits and zero active maintainers in the last three months, and was last pushed about 19 months ago. Combined with the one-release history, this is meaningful abandonment risk.
Composer is used for the build, which fits the package ecosystem. No security-scanning tooling is configured, leaving a modest transparency and maintenance gap.
The repository has no security policy. For a package integrating with an external accounting API, this weakens the documented process for reporting and handling security issues.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ^9.0 || ^10.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.