Clear documentation, repository tests, and a matching source project make integration straightforward. The package is still young, has had no commits in three months, and its workflows use unpinned actions with a high-confidence bot-condition issue.
58%
Total Score
67
100
94
50
One registry maintainer is consistent with a user-owned project, but it leaves little visible publishing redundancy, especially alongside the lack of recent repository activity.
Only two releases exist over roughly four months, with both released about a day apart. This shows the project is new and provides limited evidence of sustained maintenance.
The repository recorded zero commits and zero active maintainers in the last three months. For a package only about four months old, that is a meaningful warning about ongoing maintenance.
The repository has no security policy. This is a transparency gap for a package handling certificate signing and private-key configuration, though it is not evidence of unsafe code by itself.
All six action references are unpinned, and the audit found a high-confidence bot-condition issue in the Dependabot auto-merge workflow. Two workflows also grant top-level write permissions, which is a milder concern because no untrusted checkout or script-injection sink was found.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/contracts Version ^10.0|^11.0|^12.0 | — | — |
barryvdh/laravel-dompdf Version ^3.1 | — | — |
spatie/laravel-package-tools Version ^1.14.0 | — | — |
simplesoftwareio/simple-qrcode Version ^4.2 | — | — |
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.