Clear licensing and repository tests improve transparency, while the package has little independent adoption evidence. Security documentation and automated scanning are absent, increasing reliance on the current maintainer for future upkeep.
69%
Total Score
50
100
93
83
Only one registry maintainer is listed, which is a modest continuity concern for a user-owned project despite the package's ongoing release activity.
The registry namespace and repository are owned by the same individual, confirming direct ownership but providing no organizational handoff capacity.
All 2 recent commits came from one contributor, so maintenance is concentrated and could be disrupted if that person stops contributing.
There were 2 commits in the last 3 months, showing recent activity, but the volume is light and does not indicate a large maintenance capacity.
Composer build tooling is present, but no security scanning tools were detected, leaving automated vulnerability checks uncovered.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
bearframework/bearframework Version ^1.22 | — | — |
ivopetkov/client-packages-bearframework-addon Version 1.* | — | — |
ivopetkov/responsively-lazy-bearframework-addon Version 1.* | — | — |
ivopetkov/html-server-components-bearframework-addon Version 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.