getpop/postmeta
The source repository is active and documented, with tests present in the project and a clear license. Registry history is stale, and the package has a single active contributor despite organizational backing.
42%
Total Score
75
67
75
Health Score Breakdown
Packagist marks the entire package as abandoned and names getpop/custompostmeta as its replacement, making this release unsuitable for a new dependency despite other healthy project evidence.
The package has had no registry release in more than five years, with zero releases in the last 12 months; active repository commits partly offset this but do not restore registry maintenance.
All 18 recent commits came from one contributor, which raises continuity risk; organizational ownership provides some capacity to hand off maintenance.
The repository name does not match the package name and its README does not mention the package, creating uncertainty about whether this is the correct source repository.
The repository has no security policy, a transparency gap for reporting vulnerabilities, though this is secondary to the package's abandonment status.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Leonardo Losoviz |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 pop-schema/meta Version ^0.7.13 | — | — |
pop-schema/customposts Version ^0.7.13 | — | — |
pop-schema/migrate-custompostmeta Version ^0.7.13 | — | — |
Weekly Downloads
Info
- Last Published
- 5 years 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.