PHPackages                             chrico/wp-fields - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility &amp; Helpers](/categories/utility)
4. /
5. chrico/wp-fields

ActiveLibrary[Utility &amp; Helpers](/categories/utility)

chrico/wp-fields
================

Package which provides some re-usable fields for WordPress.

2.3.2(2y ago)1981.2k↓33.9%4GPL-2.0-or-laterPHPPHP &gt;=8.0

Since Oct 16Pushed 6mo ago2 watchersCompare

[ Source](https://github.com/Chrico/wp-fields)[ Packagist](https://packagist.org/packages/chrico/wp-fields)[ RSS](/packages/chrico-wp-fields/feed)WikiDiscussions master Synced 1mo ago

READMEChangelog (10)Dependencies (3)Versions (21)Used By (0)

ChriCo WP-Fields [![Latest Stable Version](https://camo.githubusercontent.com/062fd722e756a9e7ce2d20270f754e4f7dafcf4812fb49e831aa41fcf6be16e8/68747470733a2f2f706f7365722e707567782e6f72672f63687269636f2f77702d6669656c64732f762f737461626c65)](https://packagist.org/packages/chrico/wp-fields) [![Project Status](https://camo.githubusercontent.com/5b5a2250da48f45495a817a4bcdabb5d101fff298acebe00a55a52815b7119ed/687474703a2f2f6f70656e736f757263652e626f782e636f6d2f6261646765732f6163746976652e737667)](http://opensource.box.com/badges) [![Unit tests PHP](https://github.com/Chrico/wp-fields/actions/workflows/php-qa.yml/badge.svg)](https://github.com/Chrico/wp-fields/actions/workflows/php-qa.yml) [![License](https://camo.githubusercontent.com/18dc87863d73f8b2cca15420bb129b7a980d3b2ebc9d4fded0c2457482f477c2/68747470733a2f2f706f7365722e707567782e6f72672f63687269636f2f77702d6669656c64732f6c6963656e7365)](https://packagist.org/packages/chrico/wp-fields)
========================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================

[](#chrico-wp-fields----)

ChriCo WP-Fields is a library (not a plugin) that allows to generate form fields in WordPress.

---

Minimum requirements and dependencies
-------------------------------------

[](#minimum-requirements-and-dependencies)

ChriCo Fields requires:

- PHP 8+
- WordPress latest - 0.1
- Composer to be installed

When installed for development, via Composer, ChriCo Fields also requires:

- "phpunit/phpunit"
- "brain/monkey"

---

Docs
----

[](#docs)

Documentation can be found in [`docs/`](docs/).

---

Frequently Asked Questions
--------------------------

[](#frequently-asked-questions)

> Why are you not just using existing packages like the [Symfony Forms](http://symfony.com/doc/current/forms.html) or [Zend Form](https://framework.zend.com/manual/2.4/en/modules/zend.form.intro.html)?

That's a good question! As already mentioned above, WordPress has different pages and scenarios where to use form fields. Both packages are excellent and I worked a lot with them in past.

*But:* They need a ton of dependencies.

As example, if you're going to use Symfony Forms, you've to use other Symfony Packages like Event Dispatcher, Intl, Options Resolver, Property Access. And that's not all, if you're serious, you'll probably end up using as well [Symfony Validation](https://symfony.com/doc/current/validation.html), [Symfony CSRF](http://symfony.com/doc/current/form/csrf_protection.html), [Twig](http://twig.sensiolabs.org/). And that's the whole point..when we load half of Symfony and we're not far away from including Doctrine as well...why do we still use WordPress?

> What about WordPress Field-Plugins like [Advanced Custom Fields](https://www.advancedcustomfields.com/)?

I guess you're wrong here. ;-)

> What about the upcoming [WordPress Fields API](https://github.com/sc0ttkclark/wordpress-fields-api)?

Nothing. There's a lot of weird and quirky code in it. No interfaces, no real abstraction, no strict return types, PHP 5.2, missing Unit Tests, ... *the list is endless, so i'll stop here.*

In fact, the API will eventually appear in WordPress in near - or far - future. But until then, everything is fine. If the API is really released, I'll adapt this code to fit on top of the Fields API.

---

License
-------

[](#license)

Copyright (c) since 1987 ChriCo.

ChriCo Fields code is licensed under [GNU General Public License v3.0](/LICENSE).

```
   _____ _          _  _____
  / ____| |        (_)/ ____|
 | |    | |__  _ __ _| |     ___
 | |    | '_ \| '__| | |    / _ \
 | |____| | | | |  | | |___| (_) |
  \_____|_| |_|_|  |_|\_____\___/

```

###  Health Score

49

—

FairBetter than 95% of packages

Maintenance47

Moderate activity, may be stable

Popularity39

Limited adoption so far

Community15

Small or concentrated contributor base

Maturity77

Established project with proven stability

 Bus Factor1

Top contributor holds 91.7% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~120 days

Recently: every ~29 days

Total

20

Last Release

857d ago

Major Versions

0.3.0 → 1.02018-06-15

1.x-dev → 2.0.02023-06-19

PHP version history (2 changes)0.1.0PHP &gt;=7.0

2.0.0PHP &gt;=8.0

### Community

Maintainers

![](https://www.gravatar.com/avatar/572cb5d91b21cc9879823e849607ffe88365365391d5fd01ee4efb6a3c24df1f?d=identicon)[Chrico](/maintainers/Chrico)

---

Top Contributors

[![Chrico](https://avatars.githubusercontent.com/u/3417446?v=4)](https://github.com/Chrico "Chrico (132 commits)")[![szepeviktor](https://avatars.githubusercontent.com/u/952007?v=4)](https://github.com/szepeviktor "szepeviktor (6 commits)")[![widoz](https://avatars.githubusercontent.com/u/1917784?v=4)](https://github.com/widoz "widoz (5 commits)")[![luislard](https://avatars.githubusercontent.com/u/17932063?v=4)](https://github.com/luislard "luislard (1 commits)")

###  Code Quality

TestsPHPUnit

### Embed Badge

![Health badge](/badges/chrico-wp-fields/health.svg)

```
[![Health](https://phpackages.com/badges/chrico-wp-fields/health.svg)](https://phpackages.com/packages/chrico-wp-fields)
```

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)
