The organization backing and complete package documentation add useful continuity. Workflow references are unpinned and no security policy is published, leaving maintenance hygiene below ideal.
68%
Total Score
67
100
94
75
All four recent commits came from one contributor. Organizational ownership provides some handoff capacity, but no second active contributor is shown to reduce the current concentration.
The repository had four commits in the last 3 months, showing ongoing maintenance, but activity is relatively light for a production integration.
Composer build tooling is present, but no security-scanning tool was detected, leaving repository security hygiene less complete.
The repository has no published security policy, so users are given no documented process for reporting or handling vulnerabilities.
The single workflow was fully analyzed with no dangerous triggers, untrusted checkouts, script injection, or audit findings. However, all 3 action references are unpinned, which is a workflow supply-chain hygiene gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
monolog/monolog Version ^1.23 | — | — |
league/flysystem-ftp Version ^3.0 | — | — |
league/flysystem-sftp Version ^3.0 | — | — |
omikron/factfinder-communication-sdk Version ^0.9.9 | — | — |
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.