The package is licensed, tested, and clearly tied to an organization with a matching source repository. Its limited recent issue activity and absent security policy reduce confidence in long-term maintenance and response practices.
65%
Total Score
75
100
88
83
The package has 11 releases over about 3 years, but only one release in the last 12 months. That is usable evidence of ongoing publishing, though the recent cadence is sparse.
The repository recorded zero commits and zero active maintainers in the last three months. Although a release was published recently, the quiet commit window weakens evidence of active maintenance.
There is one open issue and one open pull request, but no issues or pull requests were created or merged in the last month. This adds a modest sign of low current activity.
Composer build tooling is present, but no security scanning tools were detected. This is a hygiene gap rather than evidence that the package is unsafe.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a transparency and response-readiness concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
ibexa/core Version ^5.0 | — | — |
ibexa/admin-ui Version * | — | — |
ibexa/content-forms 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.