Clear documentation, tests, and regular releases support adoption. The young project has limited maintenance depth and basic workflow and security gaps.
68%
Total Score
50
100
94
50
All 3 recent commits came from one contributor, giving the project a single-person maintenance dependency. The active repository helps, but does not compensate for the concentrated ownership.
The repository received 3 commits in the last 3 months, so it is active, but the volume is modest for a package handling invoicing integrations. This limits confidence in its maintenance depth.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest transparency and maintenance gap rather than evidence of a defect.
The repository has no security policy. For an integration package handling credentials and financial documents, this weakens the documented process for reporting and handling vulnerabilities.
The only workflow was fully analyzed with no injection or high-severity findings, but both action references are unpinned. The absence of a top-level permissions block is acceptable here because the workflow does not request top-level write access.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
laravel/framework Version ^12.0 || ^13.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.