doctrine/cache

The library now includes a PSR-6 cache adapter and provider, enabling interoperability with PSR-6 cache implementations. This adds new classes in the \lib/Doctrine/Common/Cache/Psr6\ directory, including \CacheAdapter\, \CacheItem\, \TypedCacheItem\, and \DoctrineProvider\, allowing users to wrap or be wrapped by PSR-6 cache pools.

lib/Doctrine/Common/Cache/Psr6 · high confidence

The Doctrine Common Cache library now provides dedicated interfaces for multi-get, multi-put, and multi-delete operations, allowing cache drivers to implement bulk retrieval and removal of cache entries. A new \MultiOperationCache\ interface combines these capabilities, and the abstract \CacheProvider\ base class implements these interfaces, enabling drivers to support efficient batched cache operations.

lib/Doctrine/Common/Cache · high confidence

All existing cache implementations (such as ApcCache, ArrayCache, MemcacheCache, and XcacheCache) are now marked as deprecated and will be removed in version 2.0. To facilitate migration, the package now includes PSR-6 and PSR-16 adapter classes (CacheAdapter and DoctrineProvider) that allow wrapping existing Doctrine cache implementations with modern standards, or wrapping PSR-6 caches as legacy Doctrine cache instances.

(repo-wide) · high confidence

Added base test case class for Doctrine tests; Added test coverage for PSR-6 cache adapter and provider; Added test suite for the ArrayCache driver and CacheProvider behavior.

The \doctrine/cache\ package is now marked as abandoned, signaling that users should migrate to alternative caching solutions. The library's \composer.json\ has been updated to require PHP 7.1 or 8.0, and dev dependencies have been upgraded to support PSR-4 autoloading, PHPUnit 7.5/8.5/9.5, and PSR-3/PSR-6/PSR-16 compatible cache interfaces.

(dependencies) · high confidence

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

• CAI 39 → 49 (+9.8)
• Rubric changed (rubric-2026.08.15 → rubric-2026.09.15) — scores are not directly comparable.

• Code Health 100 → 100 (-0.2)
• Architecture 69 → 69 (+0.0)
• Maturity 39 → 32 (-6.9)
• Readiness 27 → 51 (+23.5)
• Security 42 → 75 (+33.3)

• Coverage not measured — test suite did not build
• Dimension evaluation failed
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• No artifact signing
• No exposed public API
• No tests found
• Test reliability not included

• Duplicated block (9 lines × 2) (lib/Doctrine/Common/Cache/Psr6/CacheItem.php)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• No assertions: testDeleteMultipleNoFail (tests/Doctrine/Tests/Common/Cache/CacheProviderTest.php)
• No assertions: testSaveMultipleNoFail (tests/Doctrine/Tests/Common/Cache/CacheProviderTest.php)
• No dependency advisory monitoring
• Orphaned files with no living knowledge
• Redundant interface inheritance. CacheProvider already defines fetchMultiple, and MultiGetCache also defines it. If MultiGetCache is intended to be a mixin or interface that CacheProvider implements, the method signature is duplicated. If they are separate interfaces, clients must check for both to support multi-get, which is inconsistent with the design where CacheProvider seems to be the base interface.
• Redundant interface inheritance. Similar to fetchMultiple, saveMultiple is defined in both CacheProvider and MultiPutCache. This duplication suggests unclear interface composition or inheritance.
• Semantic ambiguity between flush and delete operations. CacheProvider exposes both flushAll() and deleteAll(), while ClearableCache only exposes deleteAll(). In caching contexts, 'flush' often implies clearing the cache namespace or resetting state, while 'delete' implies removing keys. However, in many implementations (and PSR-6), 'clear' is the standard term. Having both flushAll and deleteAll on the same interface without clear semantic distinction is confusing, and the existence of ClearableCache.deleteAll() suggests deleteAll is the preferred term for clearing, making flushAll redundant or misleading.
• Skipped (documented): testDeleteAllAndNamespaceVersioningBetweenCaches (tests/Doctrine/Tests/Common/Cache/CacheTest.php)
• Skipped (documented): testFlushAllAndNamespaceVersioningBetweenCaches (tests/Doctrine/Tests/Common/Cache/CacheTest.php)
• …and 4 more

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

doctrine/cache was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.