A README, tests, release notes, and matching source repository make the package straightforward to inspect and adopt. Its single-maintainer project has no security policy or scanning, which increases the cost of relying on an older codebase.
62%
Total Score
67
100
88
88
The package has had only one release, published about eight years ago, with no releases in the last 12 months. The repository remains available and the release includes tests and notes, but the long release gap raises abandonment and compatibility concerns.
There were no commits and no active maintainers in the last three months, consistent with a project that has seen no recent maintenance. The intact tests and repository reduce uncertainty but do not remove the risk of stale behavior.
There were no new or closed issues or pull requests in the last month, while several issues and pull requests remain open. This is supporting evidence of limited current maintenance.
Composer build tooling is present, but no security scanning tools were detected. For an older package, the lack of automated security checks is a modest transparency and maintenance gap.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a modest concern rather than evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
bcosca/fatfree Version ^3.5 | — | — |
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.