ZRCMS - Content management for version tracking and content
38%
Total Score
63
50
70
75
The package has only two releases, with none in the last 12 months, and the latest was about eight years ago. This is strong evidence of abandonment risk for a dependency.
There have been zero commits and zero active maintainers in the last three months, with the repository last pushed about eight years ago. This is the strongest evidence that maintenance has stopped.
The package declares 18 runtime dependencies, creating a substantial dependency surface for an unmaintained release. No provided signal shows that this surface is actively managed.
A README is present, and the absence of tests or a changelog in the published artifact is normal packaging practice. The short 114-character README limits consumer documentation, but this is secondary to the maintenance gap.
There are no open issues or pull requests and no recent issue or pull-request activity. While a clean tracker can be benign, here it is consistent with the absence of ongoing project activity.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
reliv/json Version ^0 | — | — |
rcm/api-lib Version ~0.10 | — | — |
reliv/locale Version ^0 | — | — |
psr/container Version ^1 | — | — |
reliv/mustache Version ^0 | — | — |
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.