Framework-agnostic page-cache control for Contenir CMS — admin writes a purge signal, Sites read it and flush.
65%
Total Score
caution
A brand-new release candidate has no recorded commit activity yet, despite an active repository and substantial release notes.
The package is effectively new: it is 0 days old with 3 releases, all published within a very short interval. This limits evidence of long-term maintenance, though the recent release activity is positive.
The repository records 0 commits and 0 active maintainers in the last 3 months. Because the package is only 0 days old and has 10 merged pull requests in the last month, this is a limited maintenance-history concern rather than strong abandonment evidence.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning coverage is a hygiene gap, not evidence that the package is unsafe.
The repository has no security policy. This reduces disclosure transparency for a package that may be used in production, although it does not by itself indicate poor maintenance.
The assessed version is a release candidate rather than a stable release, although it is the stable major line and only one-third of recent releases are prereleases. This is a moderate adoption risk rather than an abandonment signal.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
contenir/contenir-config Version ^2.1 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.