gdarko/wp-batch-processing
Documentation and release notes make integration clearer, while the small dependency surface limits maintenance complexity. The lack of a security policy and automated scanning leaves less transparency around ongoing risk.
62%
Total Score
50
100
86
50
Health Score Breakdown
The package has had no releases in the last 12 months, and its latest release was about three years ago. Its five-release history shows some maturity, but the prolonged pause raises maintenance concerns.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. This is a meaningful abandonment risk even though the repository is not archived.
Composer is used for builds, but no security-scanning tools are configured. The established build tool is positive, while the missing scanning coverage is a modest transparency gap.
The repository has no security policy, reducing transparency about vulnerability reporting and response. This is not evidence of a vulnerability, but it weakens maintenance and governance signals.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Darko Gjorgjijoski |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 3 years ago
- Created
- 4 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.