Clear documentation, tests, and licensing reduce adoption friction. The package is organization-backed, but no commits or releases for roughly three years leaves maintenance uncertain.
52%
Total Score
75
100
81
75
The package has 38 releases since January 2021, but none in the last 12 months; the latest release was about three years ago. This is a meaningful maintenance concern despite its established release history.
There were no commits and no active maintainers in the last three months, consistent with the release history showing no release for roughly three years. This materially raises maintenance and abandonment risk.
The repository name does not match the package name and its README does not mention the package. Although the package may be related to a broader project, the link does not clearly establish that this repository belongs to this release.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a hygiene gap rather than evidence that the package is unsafe to depend on.
The linked repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency gap for a package intended for integration into applications.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
pop-cms-schema/posts-wp Version ^1.0.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.