Usable with caveats: it has clear licensing, tests, documentation, and a repository that still exists, but maintenance appears effectively stopped. The last registry release was about nine years ago and the repository has had no commits in the last three months.
52%
Total Score
50
50
75
50
The project has 60 releases, but its latest release was about nine years ago and it published no releases in the last 12 months. This is strong evidence of stagnation for a library dependency.
The repository recorded zero commits and zero active maintainers in the last three months. Combined with the old latest release, this materially raises abandonment and compatibility risk.
Six runtime dependencies create meaningful compatibility and maintenance exposure, especially for a framework bundle, but the profile is not unusually large or inherently unsafe.
There are two open issues but no issues or pull requests were opened or closed in the last month, indicating little current project activity.
Composer is used for builds, which is appropriate for a Packagist package, but no security scanning tools were detected, leaving a transparency and maintenance gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
stof/doctrine-extensions-bundle Version ~1.2.1 | — | — |
open-orchestra/open-orchestra-mongo-libs Version self.version | — | — |
open-orchestra/open-orchestra-bbcode-bundle Version self.version | — | — |
open-orchestra/open-orchestra-display-bundle Version self.version | — | — |
open-orchestra/open-orchestra-model-interface Version self.version | — | — |
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.