aimeos/map

PHP arrays and collections made easy

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 54 minutes ago
Type:Library / SDKCategory(s):Core & Utility LibrariesLanguages & Runtimes
Added to GitGenius on September 16th, 2026
Created on November 18th, 2019
Open Issues & Pull Requests: 1 (+0)
GitHub issues: Enabled
Number of forks: 16
Total Stargazers: 4,322 (+0)
Total Subscribers: 8 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 10.4 hours
Mean response time: 10.4 hours
90th percentile: 10.4 hours
Tracked items: 1

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Aimeos Map is a PHP library that simplifies working with arrays and collections through an object-oriented interface.

The library addresses the friction of manipulating PHP arrays, which often requires verbose syntax and multiple function calls for common operations. It wraps arrays in a collection object that provides chainable methods for filtering, mapping, sorting, and transforming data. This approach lets developers write more readable and expressive code when working with array data, reducing boilerplate and making intent clearer.

The tool suits PHP projects where array manipulation is frequent and readability matters. It works well for applications that process lists of data, transform API responses, or perform complex filtering and aggregation operations. Developers accustomed to functional programming patterns or those working in codebases that prioritize clean, fluent interfaces will find the chainable API natural to use.

The project maintains steady activity with regular updates and bug fixes. The codebase shows consistent refinement of existing functionality rather than major architectural shifts. Documentation is actively maintained alongside code changes, keeping examples and API references current with the implementation.