Its single maintainer and install-time setup leave little visible support for long-term use. The repository could not be found, so maintenance and provenance cannot be checked; the declared proprietary license may also limit reuse.
43%
Total Score
50
100
60
50
The latest release was over two years ago, with no releases in the last 12 months. Although 24 releases show earlier activity, the current pause raises abandonment risk.
A proprietary license is explicitly declared, so the release is licensed, but it may restrict reuse compared with a typical open-source license. No license-file mismatch was detected.
The package runs a post-create-project-cmd install-time script. This may be appropriate for project setup, but it adds execution behavior that is not explained by the sparse artifact.
Only one registry maintainer is listed, leaving a thin visible ownership base if that person becomes unavailable. This is partly offset by the package's earlier release activity but remains a continuity concern.
The published artifact contains only four files, including the module entry point and Composer metadata. This may be intentional for a small module, but it offers little visible documentation or supporting material.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
genesii/wordpress-module-kernel Version 6.* | — | — |
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.