The MIT license, matching repository, and organization ownership provide useful transparency. No security policy and no automated security scanning leave weaker project safeguards.
40%
Total Score
50
67
83
The latest release was in February 2022, with no releases in the last 12 months and only three releases overall. This is strong evidence of abandonment risk for a package that may need fixes or updates.
There were no commits and no active maintainers in the last three months, after the repository had already been inactive since February 2022. This materially increases the risk that defects will remain unaddressed.
The project uses Composer and Make, which shows basic build tooling, but no security scanning tools were detected. That leaves weaker evidence of ongoing dependency and code-security hygiene.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a meaningful transparency and maintenance gap for a reusable library.
Version 0.0.3 is below a stable major version, indicating an immature public API. That concern is compounded by the long period without a newer release.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
mensbeam/framework Version ^1.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.