The organization-backed repository is active, tested, and correctly linked, but maintenance is concentrated in one contributor. The published release is old, and all six workflow action references are unpinned.
62%
Total Score
67
100
86
75
The latest registry release was published in June 2020, with no releases in the last 12 months. This materially raises staleness risk for a dependency, despite the repository showing some recent activity.
All recent commits came from one contributor. Organization backing provides some handoff capacity, but no second active contributor is shown in this period.
The repository had one commit in the last three months from one active maintainer. That is some recent activity, but it is too limited to offset the long gap in registry releases.
Composer build tooling is present, but no security scanning tool was detected. This is a modest transparency and maintenance gap rather than a standalone severe concern.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
wpdesk/wp-persistence Version ^2.0 | — | — |
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.