Repository tests, a changelog, and release notes provide useful maintenance evidence. The project is very new and has no security policy; pin the single workflow action before relying on it.
78%
Total Score
75
90
67
Five releases appeared within about 11 hours, so the package has very limited long-term release history. That limits maturity evidence but does not indicate abandonment.
There were no commits or active maintainers recorded over the last three months, but the package and repository are only hours old, so this is insufficient history rather than clear inactivity.
The repository has no published security policy. This is a transparency gap for a package that ships executable WordPress and JavaScript code, though it is not evidence of unsafe behavior by itself.
The only workflow was fully analyzed and has no dangerous triggers, untrusted checkouts, script injection, or audit findings, with job-level permissions. Its one action is unpinned, leaving a modest reproducibility and action-integrity gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
yahnis-elsts/plugin-update-checker Version ^5.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.