wpmetabox/meta-box-builder
Healthy and suitable to depend on. It has frequent releases, active work from five contributors, a matching repository, tests, and a clear license; the main caveats are low repository visibility and limited security-policy and workflow-permission hardening.
88%
Total Score
100
89
75
Health Score Breakdown
The repository has only 4 stars, 1 fork, and 2 watchers, which limits popularity-based reassurance. This is supporting evidence only and is outweighed by the package's release and commit activity.
Composer is used as a build tool, but no security-scanning tools were detected. The missing scanning automation is a modest transparency and supply-chain hygiene gap, not evidence of abandonment.
The repository has no security policy, leaving vulnerability-reporting expectations undocumented. This is a transparency gap, although active development and safe workflow analysis provide compensating evidence.
All four workflows lack top-level permission declarations. No workflow requests top-level write access, but explicitly declaring least-privilege permissions would provide stronger workflow hardening.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 elightup/twig Version ^3 | — | — |
wpmetabox/support Version ^1 | — | — |
wpmetabox/mbb-parser Version ^2.0 | — | — |
Weekly Downloads
Info
- Last Published
- 17 days 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.