symfony/cache

Provides extended PSR-6, PSR-16 (and tags) implementations

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 54 minutes ago
Added to GitGenius on September 16th, 2026
Created on January 19th, 2016
Open Issues & Pull Requests: 0 (+0)
GitHub issues: Disabled - open counts may still include pull requests.
Number of forks: 66
Total Stargazers: 4,153 (+0)
Total Subscribers: 10 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

GitHub issues are disabled for this repository, so issue analytics and the issue explorer are not available.

Detailed Description

Symfony Cache is a PHP caching component that provides extended implementations of the PSR-6 and PSR-16 standards along with tagging support.

The component solves the problem of managing application caches through a standardized interface while adding practical features beyond the base standards. It implements both PSR-6, which defines a pool-based caching interface, and PSR-16, which provides a simpler key-value caching API. The tagging feature allows developers to group related cache entries and invalidate them together, addressing a common need in real-world applications where cache invalidation must coordinate across multiple related items.

Developers should adopt this component if they need caching within a PHP application and want standards-compliant implementations with the flexibility of tagging. It suits projects that already use Symfony or those that value adherence to PHP standards while needing more than the bare PSR specifications provide. The component integrates naturally into Symfony applications but can also be used standalone in any PHP project that requires PSR-6 or PSR-16 compliance.

The project maintains active development with regular commits addressing bug fixes and feature improvements. The codebase shows consistent attention to test coverage and code quality standards. Pull requests receive timely review and feedback from maintainers. The project follows semantic versioning and maintains backward compatibility across minor versions. Documentation is kept current alongside code changes, ensuring that examples and API references reflect the actual implementation.