The package includes a clear README, repository tests, an MIT license, and no install-time scripts. Its release history is only one day old, and both workflow action references are unpinned; maintenance and supply-chain practices have little track record.
72%
Total Score
50
100
86
75
The package and repository are owned by the same individual account, providing clear ownership but no organizational backing or broader maintenance capacity.
This is the first release, published less than 1 day ago, so there is not enough history to demonstrate sustained maintenance. The repository was pushed shortly before publication, which is consistent with a new project rather than abandonment.
There were no commits or active maintainers in the measured three-month window, but the package is only one day old, so this is insufficient evidence of abandonment. It does leave maintenance capacity unproven.
Composer build tooling is present, but no security scanning tools were detected. For a new package this is a modest transparency and hygiene gap, not a severe dependency risk.
The repository has no security policy. This is a minor disclosure-process gap for a package that reads from an external WordPress database, but the available tests and README provide some compensating transparency.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
laravel/framework Version ^12.1 || ^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.