myclabs/DeepCopy

Create deep copies (clones) of your objects

View on GitHub ↗Jump to charts ↓

myclabs/DeepCopy has 8.5k+ stars and 100+ forks on GitHub, is written in PHP, and was last pushed on Aug 12, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 42 minutes ago
Type:Library / SDKCategory(s):Core & Utility LibrariesLanguages & Runtimes
Added to GitGenius on September 7th, 2026
Created on July 22nd, 2013
Open Issues & Pull Requests: 19 (+0)
GitHub issues: Enabled
Number of forks: 108
Total Stargazers: 8,885 (+0)
Total Subscribers: 27 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 9.4 hours
Mean response time: 17.6 hours
90th percentile: 2.2 days
Tracked items: 6

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 479 days
Stale 30+ days: 1
Stale 90+ days: 1

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

Sign in to see which issues are moving.
Sign in

Detailed Description

DeepCopy is a PHP library that creates deep copies of objects.

The library solves the problem of shallow copying in PHP, where cloning an object by default only copies the object itself while leaving nested objects and arrays as references to the originals. DeepCopy recursively traverses an object's properties and creates independent copies of all nested objects and arrays, ensuring that the cloned object and all its dependencies are completely independent from the original.

Developers should choose DeepCopy when working with complex object hierarchies where modifications to nested structures must not affect the original object. It suits projects that manipulate data models with deep nesting, such as those handling configuration objects, domain entities with relationships, or any scenario where true object isolation is required. The library is particularly valuable in codebases where accidental mutations of shared references could introduce subtle bugs.

The project maintains a focused scope with straightforward implementation. Development activity shows consistent engagement with the codebase through regular updates and maintenance of the core functionality.