wpmetabox/mb-acf-migration
The package includes a clear README, a small runtime dependency set, and is maintained under an organization account. Workflow references are unpinned and the repository has no security policy or scanning, leaving avoidable maintenance and build-hygiene concerns.
68%
Total Score
67
100
86
50
Health Score Breakdown
The package has 13 releases over about 18 months, but only one release in the last 12 months. That indicates a sparse cadence, although the release in July 2026 shows the project is not clearly abandoned.
All recent commits came from one contributor, creating concentration risk. The organization-owned repository provides some capacity to hand maintenance off, so this is a caution rather than a severe risk.
Only one commit was recorded in the last three months, by one active maintainer. Recent work has therefore been limited, even though the latest push is fairly recent.
The project uses Composer for builds, but no security scanning tools were detected. The build setup is established, while security-process visibility is limited.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 wpmetabox/support Version ^1 | — | — |
wpmetabox/mbb-parser Version ^2 | — | — |
Weekly Downloads
Info
- Last Published
- 2 months ago
- Created
- 5 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.