The declared GPL-3.0+ license conflicts with the BSD-3-Clause license file, so licensing should be clarified before adoption. Clear documentation, a tiny dependency footprint, and organizational ownership provide useful context, while the absent security policy is a minor transparency gap.
58%
Total Score
75
100
80
83
A GPL-3.0+ declaration is present, but the artifact and repository license file are detected as BSD-3-Clause. The package is licensed, yet the mismatch requires clarification before use.
The package has had no release in more than four years, with five releases across roughly ten years and none in the last 12 months. This is a meaningful maintenance concern, though the stable release status and small package scope partly limit the risk.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. That suggests limited ongoing maintenance capacity.
The linked repository has no security policy. For a small extension this is a transparency gap rather than a severe dependency risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
skeeks/cms-export Version * | — | — |
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.