PHPackages                             amsa/phprop - 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 & Helpers](/categories/utility)
4. /
5. amsa/phprop

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

amsa/phprop
===========

ini configuration library

1.2.0(11y ago)63.9k1GPLPHPPHP >=5.3.0

Since May 26Pushed 11y ago1 watchersCompare

[ Source](https://github.com/amsa/PHProp)[ Packagist](https://packagist.org/packages/amsa/phprop)[ RSS](/packages/amsa-phprop/feed)WikiDiscussions master Synced 1mo ago

READMEChangelogDependenciesVersions (2)Used By (0)

\#Description This package facilitates parsing and reading configurations from ini files. To create a hierarchical ini file, the only thing to do is to write keys seperated by a delimiter (by default '.') to specify parent and child. For example:

```
[application]
title="title"
db.username="username"
db.password="123"

```

You can also use a value by it's key in another configuration value:

```
[application]
url=http://localhost/my-app
login=${url}/login

```

Note: ${url} assumes *url* key is in the current section, it can be written like ${application.url}. If you want to refer to ${url} in another section (e.g. global), you should mention it as a prefix e.g. ${global.url}.
If you are using multi-level configuration keys (e.g. application.config.db.username), write the root as prefix, e.g. ${*prefix*.variable}.

\#Features

- Easy to use
- Convenient Integration
- Support for hierarchical data structure
- Section inheritance
- Array configs
- Key-value binding

\#How to use Pass the ini configuration path to the *parse* method:

```
$ini = PHProp::parse("path/to/ini");

```

If your scope delimiter is not '.', give your delimiter as the second parameter:

```
$ini = PHProp::parse("path/to/ini", "/");

```

After getting the object, the username can be accessed easily:

```
$ini->application->db->username

```

or

```
$ini['application']['db']['username']

```

To get the number of application's children:

```
count($ini->application);

```

See the samples for more.

###  Health Score

30

—

LowBetter than 64% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity23

Limited adoption so far

Community8

Small or concentrated contributor base

Maturity58

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 100% 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

Unknown

Total

1

Last Release

4375d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/a3234af8a84d952af81a4ee2bd61045e750da1ae3f50fb2b4698c2246c1b1fab?d=identicon)[amsa](/maintainers/amsa)

---

Top Contributors

[![amsa](https://avatars.githubusercontent.com/u/1153498?v=4)](https://github.com/amsa "amsa (14 commits)")

### Embed Badge

![Health badge](/badges/amsa-phprop/health.svg)

```
[![Health](https://phpackages.com/badges/amsa-phprop/health.svg)](https://phpackages.com/packages/amsa-phprop)
```

PHPackages © 2026

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