The project has had no commits or active maintainers for more than two years, and it has only six releases over its lifetime. A matching repository, clear README, MIT declaration, and release notes provide useful transparency, but do not offset the maintenance slowdown.
58%
Total Score
50
100
79
75
There were no commits and no active maintainers in the last three months, despite the repository's last push being more than two years ago. This is strong evidence of a maintenance pause and raises abandonment risk.
The package has six releases since 2019, with no releases in the last 12 months and a median interval of about 407 days. That indicates slow maintenance, although the latest release is documented and the repository remains available.
Composer is used as the build tool, but no security scanning tools are configured. The missing scanning is a hygiene gap rather than evidence that the package cannot be maintained.
The repository has no security policy. For a small WordPress helper library this is a transparency gap, though it is less significant than the prolonged lack of activity.
Version v0.0.6 is not a prerelease, but the package remains below a stable major version. This limits maturity evidence without making the release unfit on its own.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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.