The README, stable versioning, organization backing, and steady release history provide useful adoption context. Missing security scanning and a very small repository reduce confidence in long-term maintenance.
62%
Total Score
75
100
89
75
The repository recorded zero commits and zero active maintainers in the last three months. The recent release history partly offsets this, but the lack of observed source activity remains a maintenance concern.
The repository has zero stars, forks, and watchers, providing no community adoption evidence. This is only supporting evidence and does not outweigh the active release history or organization backing.
Composer is used as the build tool, but no security scanning tools were detected. That is a transparency and maintenance gap for a package handling application integration.
The repository has no security policy. This weakens vulnerability-reporting transparency, though it is a secondary concern for the overall dependency decision.
The single workflow is fully analyzed and has no reported audit findings, but it uses a top-level write token permission and its one action reference is unpinned. The pull_request_target trigger is not itself a problem because no untrusted checkout or script-injection sink was found.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
netflex/api Version ^7.0 | — | — |
illuminate/http Version ^13.0 | — | — |
netflex/support Version ^7.0 | — | — |
illuminate/queue Version ^13.0 | — | — |
illuminate/support Version ^13.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.