Risky to adopt: the latest registry release is a beta from about two years ago, with no releases in the last 12 months. The linked repository neither matches the package name nor mentions it, making ongoing maintenance and provenance difficult to verify despite tests, licensing, and build checks.
48%
Total Score
75
100
79
75
The package has had no releases in the last 12 months, and its latest release was published about 2 years and 3 months ago. This is a meaningful maintenance concern for a beta package.
The repository recorded zero commits and zero active maintainers in the last 3 months. Combined with no registry releases in the last year, this raises concern about current maintenance capacity.
The linked repository is named kensaku rather than wp-entities-search and does not mention this package in its README. That weakens confidence that the repository directly backs this release.
The repository has no security policy. This is a transparency gap, although it is less significant than the maintenance and repository-linkage concerns.
Three workflows do not declare top-level token permissions, and one declares write access. More explicit least-privilege configuration would improve workflow transparency and reduce CI risk.
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.