sebastianbergmann/environment

Provides functionality that helps writing PHP code that has runtime-specific execution paths

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 51 minutes ago
Added to GitGenius on September 9th, 2026
Created on February 10th, 2014
Open Issues & Pull Requests: 2 (+0)
GitHub issues: Enabled
Number of forks: 36
Total Stargazers: 6,765 (+0)
Total Subscribers: 5 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.9 hours
Mean response time: 444.2 days
90th percentile: 2571.7 days
Tracked items: 6

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 7% of issues opened in the past year have been closed.

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: 116 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

  • bug (4)
  • enhancement (1)
  • type/dependencies (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

sebastian/environment is a PHP library that helps detect and adapt to runtime-specific execution paths.

The library solves the problem of writing PHP code that needs to behave differently depending on whether it runs on standard PHP or HHVM, or in different execution contexts. It provides functionality to detect the runtime environment at execution time, allowing developers to conditionally execute code paths based on the detected runtime characteristics.

This tool is primarily useful for library and framework developers who need to support multiple PHP runtimes or who want to optimize code paths for specific environments. It is typically added as a development-time dependency, making it well-suited for projects that run test suites or other development tasks where runtime detection is necessary. Projects that target only a single, known runtime environment have less need for this functionality.

The project maintains a steady stream of updates and refinements. The codebase receives regular maintenance commits addressing compatibility and functionality improvements. Pull requests are reviewed and merged consistently, indicating active stewardship of the library's quality and relevance to the PHP ecosystem.